| name | clawpatch-report-only |
| description | Use when asked to run ClawPatch, review code with ClawPatch, generate a ClawPatch findings report, inspect findings, triage findings, or revalidate findings without changing source code. |
ClawPatch Report-Only
Use this skill when the user wants ClawPatch to review a repository and produce findings without applying source changes.
Safety Rules
- Default to report-only.
- Do not run
clawpatch fix unless the user explicitly asks for a fix for a specific finding.
- Before any non-dry-run fix, run
clawpatch fix --finding <id> --dry-run and show the result.
- Do not commit, push, create a PR, create a branch, create a worktree, switch branches, or run destructive git commands from this workflow.
- Use a repository-local
.clawpatch/ state directory and keep it ignored by git.
- Treat findings as candidates. Inspect evidence before recommending action.
State Directory
Run from the target repository root:
STATE_DIR=".clawpatch"
If .clawpatch/ is not ignored, add it to the repository's ignore file before running ClawPatch.
Report-Only Workflow
npx --yes clawpatch@latest --root . --state-dir "$STATE_DIR" doctor --no-input
npx --yes clawpatch@latest --root . --state-dir "$STATE_DIR" init --no-input
npx --yes clawpatch@latest --root . --state-dir "$STATE_DIR" map
npx --yes clawpatch@latest --root . --state-dir "$STATE_DIR" review --limit 3 --jobs 1 --provider codex --reasoning-effort high --no-input
npx --yes clawpatch@latest --root . --state-dir "$STATE_DIR" report -o "$STATE_DIR/review.md"
npx --yes clawpatch@latest --root . --state-dir "$STATE_DIR" next
Use --limit 3 --jobs 1 for the first pass in large repositories. Increase --limit only after the first report is useful and stable.
Inspect Findings
Show a finding before proposing a fix:
npx --yes clawpatch@latest --root . --state-dir "$STATE_DIR" show --finding <id>
Re-check a finding without editing source files:
npx --yes clawpatch@latest --root . --state-dir "$STATE_DIR" revalidate --finding <id> --provider codex --reasoning-effort high --no-input
Mark a finding without source edits:
npx --yes clawpatch@latest --root . --state-dir "$STATE_DIR" triage --finding <id> --status false-positive --note "<reason>"
If The User Explicitly Asks For Fix
Only proceed when the user names one finding or clearly points to one finding.
First run a dry run:
npx --yes clawpatch@latest --root . --state-dir "$STATE_DIR" fix --finding <id> --dry-run --provider codex --reasoning-effort high --no-input
Do not run non-dry-run fix unless the user approves that next step after seeing the dry-run result.
Final Response
Include:
- State directory and report path.
- Top findings ordered by severity and confidence.
- Which findings need human review before action.
- Any commands that failed or could not run.
- A note that no fixes, commits, branches, worktrees, pushes, or PRs were created.
