worktree-contributor

Worktree Contributor

Overview

Mode-switch skill for multi-agent collaboration. Activates contributor role at window start — from that point, all coordination runs silently in the background. The user works normally (vibe coding as usual).

Core principle: Activate once, enforce always. Zero friction after activation.

Announce at start: "Contributor role activated. All changes will go to a worktree branch. What are we building?"

Prerequisites Check

On activation, verify before anything else:

# GitHub remote is required
git remote -v | grep -q "github" || echo "ERROR: No GitHub remote. Run: git remote add origin <url>"

# gh CLI must be authenticated
gh auth status 2>/dev/null || echo "ERROR: gh CLI not authenticated. Run: gh auth login"

If either check fails, refuse to activate. Prompt user to fix.

Activation Sequence

/worktree-contributor
  → Run prerequisites check
  → Read COORDINATION.md (if exists) for situational awareness
  → Read CLAUDE.md (if exists) for persistent workflow rules
  → Set role constraints
  → Report: "Contributor role activated. What are we building?"
  → Wait for user to state goal

Hard Constraints (always enforced)

• ❌ NEVER commit to main branch
• ❌ NEVER merge to main branch
• ❌ NEVER invoke finishing-a-development-branch (merger's job)
• ❌ NEVER edit COORDINATION.md Merge Queue section except when marking own branch as ready
• ✅ ALL commits go to the worktree branch
• ✅ ALL pushes go to the feature branch remote
• ✅ PR review feedback must be addressed before marking work ready

Background Behaviors

These run automatically. The user does NOT need to know about them.

When user states a goal:

1. Derive branch name from goal: feat/xxx or fix/xxx
2. Create worktree + branch:

   git worktree add .claude/worktrees/<branch-name> -b <branch-name>
   cd .claude/worktrees/<branch-name>
   

3. Run project setup (detect from package.json etc.)
4. Analyze scope: scan relevant source directories based on the goal
5. Register in COORDINATION.md (create file if first contributor):
   • Write Branch Registry entry with scope + dependencies
   • Run conflict detection against existing entries
   • If overlap found → write Conflict Map entry + warn user
6. Push + create Draft PR:

   git push -u origin <branch-name>
   gh pr create --draft --title "<goal summary>" --body "<auto-generated description>"
   

7. Backfill PR number into COORDINATION.md
8. Record expected review mode in COORDINATION.md Review Policy / Audit Trail:
   • Remote review: GitHub automatic review on push
   • Local final review: merger-owned, provider-driven, advisory by default