g-setup

Behavior

1. Detect git

Run:

[ -d .git ]

• If .git/ exists, continue to step 2.
• If .git/ is missing, continue to step 1a.

1a. Initialize git (only when .git/ is missing)

The g-sdd pipeline requires git. Tell the user what you're about to do:

This directory is not a git repository. The g-sdd pipeline requires
git. Initializing one here.

In an interactive session, you may pause and confirm before proceeding if it feels natural ("OK to proceed?"). In auto mode, just continue — git init is benign and trivially reversible (rm -rf .git/), so it doesn't need a hard consent gate.

Run:

git init

If git init fails (e.g. git is not installed), abort with the underlying error.

On success, print exactly:

✓ git initialized.

Please fully exit and restart Claude Code, then re-run /g-setup.
The g-sdd pipeline cannot continue without git, and Claude Code
needs a session restart to detect the new repository.

Then STOP. Do not continue to step 2 — scaffolding will happen on the next /g-setup run after the user restarts Claude Code.

2. Scaffold from manifest

The manifest lives at:

${CLAUDE_SKILL_DIR}/manifest.txt

Read and parse it. Each non-blank, non-# line is one of:

• dir <path> — directory to create (relative to the project root).
• file <source> <destination> — <source> relative to ${CLAUDE_SKILL_DIR}/, <destination> relative to the project root. Always overwrites on re-run.
• file-once <source> <destination> — same path semantics as file, but strict create-if-absent: the destination is written only if it does not already exist. Used for content-bearing scaffolded files that operators populate after the first run (e.g., CONTEXT.md). See "Notes" for the full strictness boundary.

Whitespace between fields is one or more spaces or tabs.

If the manifest is missing or unreadable, abort with:

Could not read ${CLAUDE_SKILL_DIR}/manifest.txt. The
g-sdd installation may be broken — reinstall g-sdd.