Claude-skill-registry agent-ops-git-worktree
Manage git worktrees for isolated development. Create, list, remove, and work in worktrees.
install
source · Clone the upstream repo
git clone https://github.com/majiayu000/claude-skill-registry
Claude Code · Install into ~/.claude/skills/
T=$(mktemp -d) && git clone --depth=1 https://github.com/majiayu000/claude-skill-registry "$T" && mkdir -p ~/.claude/skills && cp -r "$T/skills/data/agent-ops-git-worktree" ~/.claude/skills/majiayu000-claude-skill-registry-agent-ops-git-worktree && rm -rf "$T"
manifest:
skills/data/agent-ops-git-worktree/SKILL.mdsource content
Git Worktree Workflow
When to Use
Use git worktrees when you need to:
- Work on multiple branches simultaneously without stashing
- Isolate experimental work from main repository
- Safely test changes without affecting main working tree
- Create temporary development contexts
Preconditions
exists.agent/constitution.md- Git repository initialized
- Worktrees directory exists:
(or configured in constitution)C:\dev\temp\worktrees
Procedure
Create Worktree
-
Create worktree with branch (one operation):
git worktree add <worktree-path> -b <branch-name> # Example: git worktree add C:/dev/temp/worktrees/agent-ops-feat-123 feat/feature-123 -
Verify worktree:
git worktree list # Verify directory structure ls -la <worktree-path>/.git # Should be a file (pointer to main repo .git) -
Navigate to worktree:
cd <worktree-path> # Verify correct branch git branch --show-current # Work normally (git operations work as expected) git status git add . git commit -m "feat: ..."
List Worktrees
# List all worktrees git worktree list # Detailed list with branches git worktree list --porcelain
Remove Worktree
After work is complete and merged:
# Navigate out of worktree cd <main-repo> # Remove worktree git worktree remove <worktree-path> # Delete feature branch (if merged) git branch -d <feature-branch>
Worktree Cleanup
Remove stale worktrees:
# List all worktrees git worktree list # Remove worktrees for deleted branches git worktree remove <worktree-path>
Integration with Issue Tracking
When working in a worktree:
- Update
to reflect worktree location.agent/focus.md - Track issue progress normally (updates worktree's git state)
- When committing, reference issue ID in commit message
Example Workflow
# In main repo (C:\dev\temp\agent-ops) git worktree add C:/dev/temp/worktrees/agent-ops-opencode feat/opencode-bundle # In worktree cd C:/dev/temp/worktrees/agent-ops-opencode # ... implement changes ... git add . git commit -m "feat: implement OpenCodeGenerator enhancements [FEAT-0335]" # Merge back to main cd C:/dev/temp/agent-ops git merge feat/opencode-bundle git worktree remove C:/dev/temp/worktrees/agent-ops-opencode
Scope
- ✅ Create worktrees
- ✅ List worktrees
- ✅ Remove worktrees
- ✅ Work in worktrees (normal git operations)
- ❌ Prune worktrees (use git worktree prune, which is built-in)
Notes
- Worktrees are lightweight (share same .git directory)
- Safe to delete worktree directory after removal
- No risk to main repository when working in worktree
- Perfect for feature development, bug fixes, testing
Important Rules
Never push without explicit user permission:
- Git push requires explicit user request before execution
- This is enforced by
skill and applies to all workflowsagent-ops-git - Auto-push is NEVER permitted, even for successful merges
- Always ask for confirmation before:
git push