القائمة
Use when starting feature work or before executing an implementation plan. Creates an isolated git worktree with smart directory selection and safety checks.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Update the per-session intent ledger for every user input and provide current intent as semantic context consumed by gates, skill-evolution, and jailbreak-detector. Keep intent summaries without storing raw prompts.
Use when the user asks about skill upgrades, update recommendations, or an evolution backlog; analyze io-trace and conduct_feedback to produce report-only evolution candidates. No automatic edits.
Use when an implementation plan already exists. Execute it in a separate session with review checkpoints.
Use when implementing a known feature, bug fix, or refactor with a resolved behavior contract. Requires a failing test before production code; use discovery first when the target or premise is unknown.
Use at the start of every coding or development conversation. Defines how to find and invoke coding-convention family skills. Requires relevant skills before any response, including clarification questions.
Runs after session-intent-analyzer and jailbreak-detector/downstream gate as their consumer. Decomposes the request and routes output, verification, lifecycle, and boundary skills without owning intake, raw intent inference, or tool permission.
| name | using-git-worktrees |
| description | Use when starting feature work or before executing an implementation plan. Creates an isolated git worktree with smart directory selection and safety checks. |
| compatibility | ["Python 3.11+ standard library"] |
A git worktree shares the same repository while creating an isolated workspace, so you can work on multiple branches at the same time without switching your current workspace.
Core principle: systematic directory selection plus safety verification equals reliable isolation.
Announcement at start: "I'm using the using-git-worktrees skill to set up an isolated workspace."
Follow this priority order:
# Check in priority order
ls -d .worktrees 2>/dev/null # preferred (hidden)
ls -d worktrees 2>/dev/null # alternative
If found: use that directory. If both exist, .worktrees takes priority.
grep -i "worktree.*director" CLAUDE.md 2>/dev/null
If a preference is specified: use it without asking.
If there is no directory and no CLAUDE.md preference:
No worktree directory found. Where should I create worktrees?
1. .worktrees/ (project-local, hidden)
2. ~/.config/coding-convention/worktrees/<project-name>/ (global location)
Which would you prefer?
Before creating a worktree, you must verify that the directory is ignored:
# Check whether the directory is ignored (respects local, global, and system gitignore)
git check-ignore -q .worktrees 2>/dev/null || git check-ignore -q worktrees 2>/dev/null
If it is not ignored:
Follow the project rule: fix broken things immediately.
Why this matters: it prevents accidentally committing worktree contents into the repository.
No .gitignore verification needed. It is outside the project.
project=$(basename "$(git rev-parse --show-toplevel)")
# Determine the full path
case $LOCATION in
.worktrees|worktrees)
path="$LOCATION/$BRANCH_NAME"
;;
~/.config/coding-convention/worktrees/*)
path="~/.config/coding-convention/worktrees/$project/$BRANCH_NAME"
;;
esac
# Create the worktree with a new branch
git worktree add "$path" -b "$BRANCH_NAME"
cd "$path"
Auto-detect and run the appropriate setup:
# Node.js
if [ -f package.json ]; then npm install; fi
# Rust
if [ -f Cargo.toml ]; then cargo build; fi
# Python
if [ -f requirements.txt ]; then pip install -r requirements.txt; fi
if [ -f pyproject.toml ]; then poetry install; fi
# Go
if [ -f go.mod ]; then go mod download; fi
Run the tests to ensure the worktree starts in a clean state:
# Example - use the command that fits the project
npm test
cargo test
pytest
go test ./...
On test failure: report the failure and ask whether to proceed or investigate.
On test pass: report ready.
Worktree ready at <full-path>
Tests passing (<N> tests, 0 failures)
Ready to implement <feature-name>
| Situation | Action |
|---|---|
.worktrees/ exists | use it (verify ignored) |
worktrees/ exists | use it (verify ignored) |
| both exist | use .worktrees/ |
| neither exists | check CLAUDE.md, then ask the user |
| directory not ignored | add to .gitignore and commit |
| baseline test failure | report failure and ask |
| no package.json/Cargo.toml | skip dependency install |
git check-ignore before creating a project-local worktreeYou: I'm using the using-git-worktrees skill to set up an isolated workspace.
[Check .worktrees/ - exists]
[Verify ignored - git check-ignore confirms .worktrees/ is ignored]
[Create worktree: git worktree add .worktrees/auth -b feature/auth]
[Run npm install]
[Run npm test - 47 passing]
Worktree ready at <repo>/.worktrees/auth
Tests passing (47 tests, 0 failures)
Ready to implement auth feature
Never:
Always:
Called by:
Pairs with: