Skip to content

BumpyClock/agent-templates / skills_archive/clawpatch

clawpatch

Unverified

Clawpatch review/fix/revalidate loop. Verify findings, preserve IDs, triage with evidence.

FileKindSize
SKILL.mdskill md2.9 KB
references/cli.mdmarkdown1.8 KB
references/official-docs.mdmarkdown3.3 KB
scripts/revalidate_findings.pyscript8.2 KB

references/cli.md

View on GitHub
# Clawpatch CLI

Snapshot: installed `clawpatch --help` on 2026-06-07. Exact flags -> run help.

## Global

```text
clawpatch [global flags] <command> [flags]
cmds: init map status review ci report show next triage fix open-pr revalidate doctor clean-locks
global: --root <path> --state-dir <path> --config <path> --json --plain -q/--quiet -v/--verbose --debug --no-color --no-input -h/--help --version
```

## Commands

| Cmd | Use | Key Flags |
| --- | --- | --- |
| `review` | create findings from mapped features | `--feature <id>` `--project <name-or-root>` `--limit <n>` `--since <ref>` `--include-dirty` `--jobs <n>` `--mode <default|deslopify>` `--rate-limit-per-minute <n>` `--provider <name>` `--model <name>` `--reasoning-effort <none|minimal|low|medium|high|xhigh>` `--skip-git-repo-check` `--dry-run` `--prompt-file <path|- >` `--export-tribunal-ledger <path>` `--json` |
| `show` | inspect one finding | `--finding <id>` `--json` |
| `next` | next finding by status | `--status <status>` default `open`; `--project <name-or-root>` `--json` |
| `status` | ledger summary | `--json` |
| `triage` | set finding status | `--finding <id>` `--status <open|false-positive|fixed|wont-fix|uncertain>` `--note <text>` `--json` |
| `fix` | explicit finding-scoped patch | `--finding <id>` `--provider <name>` `--model <name>` `--reasoning-effort <none|minimal|low|medium|high|xhigh>` `--skip-git-repo-check` `--dry-run` `--json` |
| `revalidate` | re-check finding(s) vs current repo | `--finding <id>` or `--since <ref>`; filters: `--all` `--status <status>` `--severity <severity>` `--feature <id>` `--category <category>` `--triage <triage>` `--limit <n>` `--include-dirty` `--provider <name>` `--model <name>` `--reasoning-effort <none|minimal|low|medium|high|xhigh>` `--skip-git-repo-check` `--json` |
receiving-code-reviewobra/superpowersUse when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementationStars: 318kUpdated Claude CodeCodexUnverifiedInstall
requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirementsStars: 318kUpdated Claude CodeCodexUnverifiedInstall
using-git-worktreesobra/superpowersUse when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallbackStars: 318kUpdated Claude CodeCodexUnverifiedInstall
verification-before-completionobra/superpowersUse when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions alwaysStars: 318kUpdated Claude CodeCodexUnverifiedInstall