Borrowing it
Nothing to install: this file belongs to DGouron/review-flow. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/DGouron/review-flow/master/.claude/skills/worktree/SKILL.mdgit clone --depth 1 https://github.com/DGouron/review-flowWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/dgouron/review-flow/worktree)<a href="https://agentmods.dev/skills/dgouron/review-flow/worktree"><img src="https://agentmods.dev/badge/skills/dgouron/review-flow/worktree/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/dgouron/review-flow/worktree"><img src="https://agentmods.dev/badge/skills/dgouron/review-flow/worktree.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Tool Misuse · line 118 Tool parameters are crafted to achieve unintended or unsafe behavior. Parameter abuse can bypass intended safety checks (e.g. shell=True, --force, dangerous glob patterns).Fix: Validate all tool parameters against an allowlist. Reject dangerous parameter values (shell=True, --force, -rf /) and use safe defaults.
What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00034 | $0.01140 |
| Opus 5.5 | $0.00014 | $0.00456 |
| Sonnet 5.5 | $0.00007 | $0.00228 |
| Haiku 4.5 | $0.00003 | $0.00114 |
Grade A, and why
worktree scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2mo ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 192 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Command /worktree - Git Worktree Management
Manages Git worktrees for working on multiple branches in parallel across different Claude Code sessions.
Absolute Security Rules
NEVER push directly to `master`!
NEVER commit directly to `master`!
Only allowed action on `master`: git pull origin master
Always create a PR to merge into `master`
Configuration
| Parameter | Value |
|---|---|
| Worktrees directory | .claude/worktrees/ |
| Main branch | master |
Default --from branch |
master |
Subcommands
/worktree or /worktree list
Lists all existing worktrees with their branch and status.
/worktree add <name> [--from <branch>]
Creates a new worktree with a "home-base" branch.
- By default, based on
master - Path:
.claude/worktrees/<name>
/worktree remove <name>
Removes a worktree (asks for confirmation if not clean).
/worktree sync [name]
Synchronizes the worktree with master (pull only).
/worktree connect <name>
Changes the current session's working directory to the specified worktree.
- Verifies the worktree exists
- Moves into
<worktree_path> - Displays the worktree's git status
Worktree Architecture
claude-review-automation/ <- Main worktree (master)
├── src/
├── .claude/
│ └── worktrees/
│ ├── refactor/ <- Refactor worktree
│ │ ├── src/
│ │ └── ...
│ ├── debug/ <- Debug worktree
│ │ ├── src/
│ │ └── ...
│ └── feature-x/ <- Feature worktree
│ ├── src/
│ └── ...
└── ...
Concept: "Home-Base" Branches
Each worktree has a "home-base" branch that serves as a starting point.
| Branch | Role |
|---|---|
refactor, debug, etc. |
Worktree home-base (synced with master) |
feat/xxx-*, fix/xxx-* |
Working branches |
Workflow inside a worktree:
# 1. You are on the home-base (e.g., refactor)
git status # On the refactor branch
# 2. Create a feature branch for your ticket
git checkout -b feat/xxx-description
# 3. Work, commit...
git add .
git commit -m "feat(scope): description"
# 4. Push the feature branch (NEVER the home-base)
git push origin feat/xxx-description
# 5. Create a PR to master (via gh CLI)
# 6. Once merged, return to home-base and sync
git checkout refactor
git pull origin master
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 2mo ago First seen · 192 lines · 34 tokens per session scan A 03b8481ce48c
worktree is a skill published in the GitHub repository DGouron/review-flow (44 stars, last pushed today), licensed MIT. It adds 34 tokens to every session and 1,140 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
release
Cut a brooks-lint release: set the version in package.json, propagate it across all four plugin manifests and every version-bearing text file (README badges, docs site metadata), write the CHANGELOG entry, validate, then commit, push, tag, and publish the GitHub release. Triggers when the maintainer asks to "release"…
address-review
Read PR review comments from GitHub, evaluate, address, and reply.
git-workflow
Git workflow and conventional commits. Use when working with git, branches, commits, pull requests, code review, or version control strategy.
code-review
Review PR, branch, commit or working-tree changes for concrete defects and fidelity to intended behavior. Also use when explicitly asked to independently challenge a prepared plan, diagnosis or verification claim.
workflow-pr-review
Use when reviewing a remote GitHub PR — a first-pass peer review, or a followup re-check after the owner has addressed feedback. Fetches into an ephemeral worktree, runs the reviewer agent against the updated diff with a Review Decision footer instruction, deduplicates findings against existing review threads (±5-line…
workflow-address-feedback
Use when a PR owner wants to address review feedback — fetches outstanding threads and general comments, presents a per-item triage (ADDRESSED / CLARIFIED / DEFERRED), applies fixes via the Edit tool, commits via workflow-commit-and-pr, resolves review threads via GraphQL resolveReviewThread (those without a thread…