dna_gg

The DNA layer for the gg CLI workflow: ticket, commit, push, review, publish.

Guides

• dna/doc/guides/develop-guide.md, dna/doc/guides/develop-without-ai-guide.md — the ticket driven workflow, with and without an AI
• dna/doc/guides/for-ai/ai-dev-guide.md — the same workflow as instructions for an agent. Its section "Keep every repo in its scope" makes the agent propose on its own to split a repo, add a new or an existing one, or move code, whenever code leaves the scope of its repo — and its section "Keep the index.jsonc up to date" makes it update the index.jsonc with every code change that alters what the repo does or uses, and create it in every repo of a ticket that has none yet. Its section "Describe every repo in its own terms" keeps the parent repos of a ticket out of what the agent writes into their dependencies: commit and merge messages, changelog, blog posts, code comments, index.jsonc
• dna/doc/guides/install-guide/install-gg-guide.md, dna/doc/guides/install-guide/install-gg-workspace-guide.md — install gg and set up a workspace

CLAUDE.md

• dna/CLAUDE.md — points the agent to the ai-dev-guide and the skills. helix writes it into the managed block of the consumer's CLAUDE.md (<!-- helix:claude_md:start/end -->), everything outside the block stays with the repo.

Skills

All skills of this layer are prefixed with gg-:

• /gg — lists the skills below and says which one comes next
• /gg-ticket — creates a ticket, adds the repos it needs and keeps every repo in its scope
• /gg-commit — proposes a message and commits through gg do commit
• /gg-push — pushes the ticket branches
• /gg-review — checks the scope of every repo, writes the blog posts and opens the pull requests
• /gg-publish — releases the ticket
• /gg-cleanup — removes what the ticket left behind

Hooks

• dna/dot-claude/settings.json — runs .claude/hooks/pm-prompts.mjs on the Claude Code hooks SessionStart, UserPromptSubmit and SessionEnd
• dna/dot-claude/hooks/pm-prompts.mjs — keeps every prompt written to Claude Code in the project management repo dnaPmRepo names. The prompts wait in ~/.claude/pm-prompts/sessions/ and are committed to the branch prompts of that repo when a session starts or ends, under doc/prompts/<first name>/<yyyy-mm>/<yyyy-mm-dd>_<repo>_<session>.md. The first name comes from the Git line of doc/team/people.md there, an unknown email goes to doc/prompts/_unknown/. Only the prompts are kept, never the answers; tokens and passwords are replaced by [redacted]. No working tree is touched: the commit is built in a bare cache below ~/.claude/pm-prompts/repos/. Needs node and git; a failure never stops a prompt and ends up in ~/.claude/pm-prompts/sync.log.
• dna/dot-claude/hooks/pm-prompts.json — the name of the project management repo, dnaPmRepo. Empty, nothing is kept. In a folder that holds several repos, like a gg ticket, the prompts go to the project management repos those repos name.

A repo with a .claude/settings.json of its own moves its settings to dna/dot-claude/settings.overrides.json, otherwise the DNA overwrites them. Arrays are appended with a + after the key, e.g. "SessionStart+": [ … ] below "hooks".

Scripts

• dna/scripts/delete-feature-branch.js — the one script this layer calls itself, from /gg-cleanup, with the two functions it imports: dna/scripts/functions/colors.js and dna/scripts/functions/run-command.js

These three files are byte-identical copies of their originals in dna_scripts. They are duplicated on purpose so that this layer does not drag the whole script set into every repo that only wants the gg workflow. A repo that wants the full set lists dna_scripts as a layer of its own — the copies are identical, so both layers together produce exactly the same files.

Layers

Builds on dna_install for the install overview and dna_index for the repo index every gg repo keeps.

It extends the @tooling section of the install overview through dna/doc/guides/install-guide.overrides.md: it adds Install gg and appends the Workspace section.

Variables

• dnaCopyrightHolder — the name in the license header of every file
• dnaCompany, dnaGitOrg, dnaGitOrgUrl — the organization repos are created in
• dnaJiraPrefix — the prefix of a ticket id
• dnaGitQuickCheckPipelineName — the name the branch rules require
• dnaPubDevPublisher — the pub.dev publisher packages are transferred to
• dnaPmRepo — the project management repo the prompts go to: its name with .git appended, e.g. my_pm.git, which finds it beside the repo's own origin, or a full git URL. helix re-cases a bare name like my_pm to the case of the reference, .git keeps it as written. Empty by default, then no prompt is kept

dnaCopyrightHolder, dnaCompany and dnaJiraPrefix name the organization, so they are never inherited: every layer or project listing this one sets them in its own dna/_vars.json. helix init and helix add ask for the missing ones.

Usage

Declare it as a dev-dependency and initialize once:

pnpm add -D @ggdna/dna-gg   # TypeScript projects
dart pub add dev:dna_gg     # Dart projects
helix init

The placed test instantiates and verifies the DNA on every test run.

Development

The dna/ folder is hand-authored source and is never generated. The repo instantiates its own DNA — run dart test after changes; commit first, a file the DNA would overwrite must not carry uncommitted work.