notque/vexjoy-agent / skills/meta/do
do
VerifiedClassify user requests and route to the correct skill, pipeline, and stack. Primary entry point for all delegated work.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 31.2 KB |
| references/antigravity-execution.md | markdown | 21.2 KB |
| references/error-handling.md | markdown | 478 B |
| references/execution-architecture.md | markdown | 1.2 KB |
| references/hooks-guide.md | markdown | 2.7 KB |
| references/lazy-completion-detector.md | markdown | 2.2 KB |
| references/model-selection.md | markdown | 8.4 KB |
| references/parallel-analysis.md | markdown | 13.4 KB |
| references/perspective-prompts.md | markdown | 5.8 KB |
| references/pipeline-guide.md | markdown | 1.6 KB |
| references/planning-guide.md | markdown | 1.2 KB |
| references/progressive-depth.md | markdown | 5.4 KB |
| references/quality-gates.md | markdown | 536 B |
| references/quality-loop.md | markdown | 6.8 KB |
| references/repo-architecture.md | markdown | 4.9 KB |
| references/routing-telemetry.md | markdown | 4.6 KB |
| references/semantic-first-ab-results.md | markdown | 1.6 KB |
| references/workflow-dispatch.md | markdown | 9.5 KB |
| references/worktree-rules.md | markdown | 5.0 KB |
references/worktree-rules.md
View on GitHub# Worktree Agent Rules
> From the demoted `worktree-agent` skill. Canonical worktree isolation rules for agents dispatched with `isolation: "worktree"`.
Mandatory rules for any agent dispatched with `isolation: "worktree"`.
## Rule 1: Verify Your Working Directory
Run `bash scripts/worktree-preflight.sh <intended-branch-name>`. Verify Git identifies this checkout as a linked worktree on the assigned feature branch. The directory may be under `.claude/worktrees/`, `/tmp`, or another assigned location. Stop if this is the main checkout or a different task’s branch.
## Rule 2: Create Feature Branch First
```bash
git checkout -b <branch-name>
```
Use an existing assigned feature branch when it is already checked out here. Otherwise create a unique branch before editing. Do not delete a collided branch or update another active worker's branch. Coordinate with its owner or choose another name.
After a merge command reports a local checkout error, verify the PR state on GitHub before reporting a merge or retrying it.
## 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.
## Rule 9: Run Preflight Check on Start
Run the preflight script at the start of any worktree task to confirm clean state:
```bash
bash scripts/worktree-preflight.sh <intended-branch-name>
```
If it exits 1, fix the reported issue before proceeding.
## Rule 10: Reserve disk capacity before creating a checkout
The dispatcher runs this before each implementation worktree:
```bash
python3 ~/.claude/skills/process/scripts/worktree_capacity.py \
--repo "$(git rev-parse --show-toplevel)" --strict
```
| State | Dispatcher action |
|---|---|
| `ready` (<80% used) | Create the one implementation checkout for the candidate. |
| `cleanup-soon` (80–<85%) | Reclaim accepted clean checkouts before adding another. Use root read-only review work where possible. |
| `blocked` (≥85%) | Integrate, deploy, verify, or reclaim; create no new checkout. |
The report lists clean candidates only. The dispatcher confirms their task is inactive before removal.
## Rule 11: Assign checkout roles deliberately
| Task | Checkout policy |
|---|---|
| Source implementation or repair | One writable task worktree, reused through review corrections. |
| Code review, test-plan review, or read-only investigation | Read the candidate through `git diff` or `git show` from the repository root; allocate no checkout. |
| Large repository implementation | Create a sparse worktree containing declared source/test/config scopes; include whole-repository content only when the task requires it. |
```bash
git worktree add --no-checkout <worktree-path> -b <branch> <base-sha>
git -C <worktree-path> sparse-checkout init --no-cone
git -C <worktree-path> sparse-checkout set --no-cone <declared-path>...
git -C <worktree-path> checkout
```
Record any full-checkout reason in the dispatch handoff.
## Post-Merge Cleanup
After integration or a PR merge, the dispatcher confirms the task is inactive and the checkout is clean, then runs:
```bash
git worktree remove -- <accepted-worktree-path>
bash scripts/worktree-cleanup.sh --force
```
`git worktree remove` frees the materialized checkout while preserving its branch for recovery. The cleanup script then prunes stale records and removes merged harness branches.
## 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 |
| New task fails to create worktree | 9 | Branch name collision from prior stale run |
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| writing-skillsobra/superpowersUse when creating new skills, editing existing skills, or verifying skills work before deployment | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| xlsxanthropics/skillsUse this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .xltx, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like "the xlsx in my downloads") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| shipping-and-launchaddyosmani/agent-skillsPrepares production launches. Use when preparing to deploy to production, or when asking what needs to be in place before shipping. Use when you need a pre-launch checklist, when setting up monitoring, when planning a staged rollout, or when you need a rollback strategy. | Stars: 119k | Updated | Claude CodeCodex | Verified | Install |
| childhoodthedotmack/claude-memBabysit a shipped release after merge, publication, or deployment. Verify published packages, production behavior, installed plugins, and late CI or user reports until the observation window is clean; use babysit for PR readiness before release. | Stars: 118k | Updated | Claude CodeCodex | Verified | Install |