메뉴
Auto-create git worktrees for workflows. Isolate changes, merge on success, discard on failure.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
| name | git-worktree |
| description | Auto-create git worktrees for workflows. Isolate changes, merge on success, discard on failure. |
| autoInvoke | false |
| priority | medium |
| triggers | ["workflow:start","worktree","isolated branch"] |
| allowed-tools | Bash, Read, Write |
| user-invocable | false |
AI-consumed reference. Optimized for Claude to read during execution. Human-readable explanation: see docs/architecture/HIERARCHICAL_PLANNING.md or docs/getting-started/ depending on topic.
Auto-create git worktree when starting a workflow. All changes on isolated branch. Discard on failure -- zero damage to main.
/run when AF_WORKTREE=trueworktree_lifecycle[5]{event,action}:
run:start,"git worktree add .worktrees/[id] -b af/[id]"
Phase 1 approved,All edits in worktree directory
Phase 5 complete,"Offer: merge / create PR / keep branch / discard"
run:cancel,"git worktree remove .worktrees/[id]"
run failed,Discard worktree — main untouched
export AF_WORKTREE=true
export AF_WORKTREE_DIR=".worktrees" # default
Add .worktrees/ to .gitignore.
safety[4]{rule,reason}:
Never force-delete with uncommitted changes,User may lose work
Always offer merge/PR/keep/discard,User decides
Auto-discard only on explicit cancel/failure,Don't assume
Checkpoint commits before discarding,Last chance to recover
Works with phase-checkpoint.cjs -- checkpoints are commits on worktree branch, main never affected until explicit merge.
CRITICAL: MUST run for EVERY message. Detects agent, complexity, AND model automatically. Without this, tasks route to wrong agents and use wrong models, degrading quality and wasting tokens.
5 techniques for different problem types. Use when stuck or facing complex challenges.
Structured thinking process for complex analysis. Supports revision, branching, and dynamic adjustment.
Angular 17+ gotchas and decision criteria. Covers signals vs observables, standalone patterns, and common pitfalls Claude gets wrong.
Designs RESTful APIs with endpoint naming, versioning strategies (URL path, header-based), pagination (offset and cursor), error response schemas, and OpenAPI conventions. Use when the user asks about REST API design, creating endpoints, URL structure, API versioning, status codes, Swagger, or OpenAPI specs.
Fast bug fixes with root cause investigation + TDD. Enforces 'no fix without root cause' discipline and verification protocol. Without this skill, fixes are applied at symptoms instead of sources, and bugs return.