Git Repo

Git repository management and SourceGit GUI client integration.

Topics

Topic Dependencies

worktree (entry point — inventory + decision)
  └─→ rename-worktree (reuse registered worktree)
  └─→ move-worktree (register unregistered or relocate)

Worktree decision tree (HARD STOP — every time a worktree is needed)

Whenever a worktree is needed (plan/build/test without switching branches, PR verification, isolated work environment, new commit while main branch has another in-flight task), check for inactive worktree reuse before creating a new one.

Flow

1. git -C worktree list to enumerate existing worktrees
2. Identify inactive candidates:
• Merged-PR worktrees (commit hash equals the base branch's merge commit)
• Stale fix/refactor branch worktrees (confirm with the user)
3. If an inactive worktree exists → reuse via the rename-worktree topic (rename the directory + metadata, switch branch)
4. If no inactive worktree exists or the user opts for new → git worktree add

New-commit-start trigger (HARD STOP — paired with git.md)

When committing new work on a main/master/develop branch, if git status shows uncommitted changes from another task, worktree splitting is mandatory.

Entry conditions (any one)

• Current branch = main/master/develop
• git status shows 1+ changed files outside the new work (e.g., another task's unstaged files)
• Unpushed commits include another task's work

Decision tree on entry

git status (check for other changes)
  ├─ 0 other changes, branch = PR/feature → commit in place
  ├─ 0 other changes, branch = main/master/develop
  │    → AskUserQuestion: (a) create PR branch from current (b) create PR branch in a new worktree
  ├─ 1+ other changes, branch = main/master/develop
  │    → worktree split required. Leave other changes in place, isolate new work in a new worktree
  └─ Another task running on a PR branch with stray changes on main
       → Report to the user (confirm intent of stray changes) → decide worktree split + stray cleanup

Worktree split procedure

1. Leave the new work's diff in place — do NOT stash (preserve the working directory)
2. git -C worktree list to inspect inactive worktrees (per the decision tree above)
3. Inactive candidate present → reuse via rename-worktree; otherwise git -C worktree add .claude/worktrees/ (or the worktree path defined by the active environment context — see worktree.md "Default Path Rules")
4. cd into the new worktree, then git checkout -b (or use the existing inactive branch)
5. Re-apply the same diff in the new worktree via Edit (the original main changes stay on main)
6. add → commit → push → PR inside the new worktree

Don't / Do

Don't / Do

Recommended placement rule (HARD STOP — prevent 2nd recurrence)

When building AskUserQuestion options for worktree selection:

The Recommended marker must attach to the reuse option. "Safer to default to new because purpose is unclear" is an autonomous judgment — instead, document the "verify current commit/branch before reuse" procedure in the rename option description so the user can decide.

Self-check (before any worktree work)

1. Did you call git -C worktree list?
2. Does any worktree in the output match (a) the same commit as HEAD or (b) a merge commit hash? → inactive candidate
3. If inactive candidates exist, include both the new-add option and the reuse option in AskUserQuestion
4. Is the Recommended marker attached to the reuse option? (apply the "Recommended placement rule" table)
5. Use new-add only when 0 inactive candidates exist OR the user explicitly chose new

Typical failure mode

When a worktree is needed for plan verification, defaulting to "create new + remove later" wastes resources. git worktree list often shows merged-PR worktrees stuck on the merge commit hash — these are reuse candidates. Always inventory first before creating a new worktree.

Quick Reference

ghq Clone (automatic SourceGit registration)

When ghq get is executed, the following happens automatically:

1. Clone the repository
2. Register in SourceGit (under the appropriate group)
3. Auto-create the group if it doesn't exist

Proceeds automatically without user confirmation

Detailed guide

SourceGit Management

Directly edit the SourceGit GUI client's configuration file to add repositories, create workspaces, rename folders, etc.

Key features:

• Add/remove repositories
• Create workspaces
• Sync ghq repositories
• Update paths on folder rename

Detailed guide

ghq Migration

Migrate regular Git repositories to ghq directory structure (~/ghq/host/group/repo/).

Key features:

• Automatic bare+worktree structure conversion
• Create symbolic links at original location
• Nested group support (host/group/subgroup/repo)

Detailed guide

Repo Patrol (batch inspection)

Batch inspect and clean up the status of repositories under ghq.

Key features:

• Parallel collection of status, stash, unpushed for all repositories
• Status-based processing (commit-splitter integration, stash pop, push)
• Optional fetch all at the end

Detailed guide

Common Workflow

1. Repository migration: Migrate to ghq structure with migrate topic
2. SourceGit update: Register new paths with sourcegit topic
3. Batch inspection: Clean up uncommitted/unpushed changes with patrol topic

Scripts

• ./scripts/repo-to-ghq.sh - Script to move repositories to ghq path