Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →tmchow/clawpatch
This skill is specifically for the Clawpatch CLI (openclaw/clawpatch, https://clawpatch.ai) — an npm-installed automated code-review and per-finding fix tool. Use it ONLY when Clawpatch itself is in play: the user says "review with clawpatch", "run clawpatch", "clawpatch fix", "find bugs with clawpatch", "clawpatch report/findings", "clawpatch open-pr", wants to dispatch subagents to fix Clawpatch findings in parallel, or otherwise names Clawpatch or one of its commands.
Passed 20 of 22 test cases with the skill, and 5 of 22 without it.
and 16 more in the full report
15 fixed5 passed either way2 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 15 test cases the skill fixed. Same model, same prompt, with and without the skill.
After `clawpatch fix` successfully applies and validates a patch for finding `f_99`, what status does the finding hold in `.clawpatch/`, and how should we confirm its resolution?
| Checked | Without skill | With skill |
|---|---|---|
| Identifies that `clawpatch fix` transitions finding status to `uncertain`. | Missed | Passed |
| Executes `clawpatch revalidate --finding f_99` to confirm resolution. | Missed | Passed |
The instructions your model reads when the skill loads.
Clawpatch (
openclaw/clawpatch, https://clawpatch.ai) is an agent-driven CLI: it reviews a repo into structured findings and can apply validated per-finding fixes. It needs Node.js 22+ and a provider CLI (codex by default);fixrefuses dirty source worktrees by default, whilereview/ci/revalidatecan include dirty code when explicitly scoped.This skill is judgment + orchestration, not a CLI reference. For exact flags, JSON fields, and exit codes, trust
clawpatch <cmd> --helpand the live--jsonoutput over anything written here — Clawpatch is pre-1.0 and its surface drifts, so a written copy will mislead. What this skill carries is what--helpcan't tell you: when to reach for it, how to fix findings in parallel, and the traps.
Use Clawpatch when the user names it, or wants whole-repo automated review that yields locatable findings plus optional validated fixes.
Don't use it for: a small diff already under review (a whole-repo review cycle
is overkill — use a diff-review tool); a bug the user already understands and
just wants written; or when no provider CLI (codex/claude/cursor/grok/
opencode/pi/acpx, or mock for tests) is installed — clawpatch doctor
fails fast, so say so and stop.
clawpatch doctor verifies the install and the provider. The published CLI
requires Node.js 22+. If clawpatch is missing, install the current published
package (npm install -g [email protected]). The provider (codex by default) is
the user's to install and authenticate — don't run login flows on their behalf.
Gitignore .clawpatch/ early to keep status, commits, and PR diffs clean.
Clawpatch allows its own state directory to change during runs; fix's dirty
guard is for source worktree changes, not .clawpatch/ churn. Add the single
line .clawpatch/ before review/fix when the repo doesn't already ignore it,
but remember .gitignore is tracked — confirm with the user before editing it.
test cases passed, vs 5 / 22 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.