القائمة
Use when starting feature work that needs isolation, before executing plans in parallel, or when working on multiple branches simultaneously — creates and manages git worktrees
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Use before any creative work, new features, architecture changes, or behavior modifications — explores intent, constraints, and design before implementation begins
Execute an implementation plan using the coordinator pattern — per task, dispatch implementer → spec-reviewer → code-quality-reviewer; per wave, synthesize and verify. Parallel where independent, sequential where dependent. Use when you have a plan ready to execute.
Use during brainstorming when visual content would help — mockups, wireframes, layout comparisons, architecture diagrams. Zero-dependency, no server required.
Systematic debugging with hypothesis tracking, evidence collection, and checkpoint management. Use when encountering any bug, test failure, or unexpected behavior — diagnoses before fixing.
Use when implementation is complete and you need to merge, create a PR, keep, or discard a branch — handles integration and cleanup after development work
Use when creating new Athena skills, editing existing skills, or building skills for any Claude Code plugin — guides skill authoring with TDD validation
| name | athena-worktree |
| description | Use when starting feature work that needs isolation, before executing plans in parallel, or when working on multiple branches simultaneously — creates and manages git worktrees |
You create isolated git worktrees for safe parallel development. Fast defaults, minimal ceremony, works on Windows and Unix.
Use this priority order — stop at the first match:
.worktrees/ or worktrees/ in project root. If found, use it..worktrees/ in project root (hidden, clean).No questions needed — the defaults are good.
GATE: For project-local directories, verify the worktree directory is git-ignored before proceeding.
git check-ignore -q .worktrees 2>/dev/null
If NOT ignored: Add to .gitignore and commit immediately. Then proceed.
Why: Prevents accidentally committing worktree contents to the repository.
Also verify that .athena-state.json and .athena-edit-burst.json are git-ignored (these are Athena internal state files that should not be committed).
# Get project name for context
project=$(basename "$(git rev-parse --show-toplevel)")
# Create worktree with new branch
git worktree add ".worktrees/$BRANCH_NAME" -b "$BRANCH_NAME"
cd ".worktrees/$BRANCH_NAME"
Branch naming: Use descriptive names — feature/auth, fix/rate-limit, refactor/config. Match the project's existing convention if one exists.
Auto-detect and run the appropriate setup:
| File Found | Command |
|---|---|
package.json | npm install |
requirements.txt | pip install -r requirements.txt |
pyproject.toml | pip install -e . or poetry install |
Cargo.toml | cargo build |
go.mod | go mod download |
| None | Skip setup |
Run the project's test suite to confirm the worktree starts clean:
# Use project-appropriate command
pytest / npm test / cargo test / go test ./...
If tests fail: Report failures. Ask whether to proceed or investigate. If tests pass: Report ready.
Worktree ready
Path: <full-path>
Branch: <branch-name>
Tests: <N> passing, 0 failures
Ready to implement <feature-name>
git worktree list
# After merging or discarding the branch
git worktree remove .worktrees/<branch-name>
git branch -d <branch-name> # or -D to force
git worktree prune
Windows: Git worktrees work natively. Use forward slashes in paths. Symlinks may require Developer Mode enabled.
CI/CD: Worktrees share the same .git directory — don't run parallel CI jobs in the same repository without separate clones.
git worktree prune periodically