worktree-agent
$
npx mdskill add notque/vexjoy-agent/worktree-agentEnforces isolation rules for agents using git worktrees
- Ensures agents operate in isolated git worktree directories
- Relies on git commands and file system checks for validation
- Applies mandatory rules for branch creation and path handling
- Prevents interference with main repository through strict path constraints
SKILL.md
.github/skills/worktree-agentView on GitHub ↗
---
name: worktree-agent
description: "Mandatory rules for agents in git worktree isolation."
user-invocable: false
context: fork
tags: [worktree, isolation, parallel, agent]
routing:
triggers:
- "worktree agent"
- "git worktree"
- "git worktree rules"
- "isolated agent"
category: git-workflow
---
# Worktree Agent Rules
Mandatory rules for any agent dispatched with `isolation: "worktree"`.
## Rule 1: Verify Your Working Directory
On start, run `pwd`. Your path MUST contain `.claude/worktrees/`.
If your CWD is the main repo path, **STOP** and report the error.
## Rule 2: Create Feature Branch First
```bash
git checkout -b <branch-name>
```
Never commit on the default `worktree-agent-*` branch. Create your feature branch FIRST.
## Rule 3: Use Worktree-Relative Paths
Never hardcode absolute paths from the main repo. Use `$(git rev-parse --show-toplevel)/path`.
**Exception**: Reading gitignored ADR files requires the main repo absolute path.
## Rule 4: Ignore Auto-Plan Hooks
Keep planning inline instead of creating `task_plan.md`. If the auto-plan hook fires, continue with the current task and keep your attention on implementation.
## Rule 5: Stage Specific Files Only
```bash
git add path/to/specific/file.py
```
Never `git add .`, `git add -A`, or `git add --all`. Verify with `git diff --cached --stat`.
## Rule 6: Do Not Touch the Main Worktree
Never write to paths outside your worktree directory. Never run `git checkout` in the main repo.
## Rule 7: Commit with Conventional Format
Use the commit message specified in your prompt. No attribution lines.
## Rule 8: Run Both ruff Checks Before Declaring CI-Ready
For any Python code changes, run both checks before pushing or creating a PR:
```bash
ruff check . --config pyproject.toml
ruff format --check . --config pyproject.toml
```
Running only `ruff check` misses formatting violations. The `Tests / lint` CI job runs both — if you skip `ruff format --check`, the PR will fail CI and cannot merge due to branch protection.
## Failure Modes This Prevents
| Failure | Rule | Without It |
|---------|------|-----------|
| Agent edits main repo files | 1, 6 | Changes leak to main, get stashed/lost |
| Context wasted on task_plan.md | 4 | Implementation budget consumed by planning |
| Commit on wrong branch | 2 | Orchestrator merges wrong content |
| PR has changes from 2 ADRs | 5, 6 | Cross-contamination between agents |
| Branch locked by worktree | 2 | Fatal error on checkout |
| PR fails CI on format | 8 | Merge blocked; `ruff format --check` was skipped |
More from notque/vexjoy-agent
- adr-consultationMulti-agent consultation for architecture decisions.
- agent-comparisonA/B test agent variants for quality and token cost.
- agent-evaluationEvaluate agents and skills for quality and standards compliance.
- architecture-deepeningProactive architecture improvement: find shallow modules, propose deepening opportunities, design conversation.
- auto-dreamBackground memory consolidation and learning graduation — overnight knowledge lifecycle.
- bluesky-readerRead public Bluesky feeds via AT Protocol API.
- cobalt-coreCobalt Core infrastructure knowledge: KVM exporters, hypervisor tooling, OpenStack compute.
- code-cleanupDetect stale TODOs, unused imports, and dead code.
- code-lintingRun Python (ruff) and JavaScript (Biome) linting.
- codebase-analyzerStatistical rule discovery from Go codebase patterns.