Review task done
Run metareview's deterministic task-done code review gate before claiming a local task is complete; use for task closure, chunk review, or pre-PR local review when code changed.From its SKILL.md
npx -y skills add dsifry/metareview --skill review-task-doneAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 23 stars23 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
1.4 KB, as published. Nobody here has run it
Review Task Done
Run this before saying a coding task is done.
Command
metareview review task-done <task-id-or-path> [--base <ref>] [--previous-run <run-id>] [--max-attempts <n>] [--evidence <path>]
Use --base for the reviewed diff, --previous-run after fixes, and --evidence for validation output. Use --max-attempts only on the first run; it sets the chain budget (default 3), with the first blocker run as attempt 1.
Prefer structured evidence receipts:
go run ./cmd/metareview evidence run -- go test ./...
Freeform evidence remains accepted as a fallback, but receipts preserve command, exit code, timestamps, and output hashes.
Workflow
- Run the command from the repository root.
- Exit handling:
0means verifyPASS/PASS_ADVISORYwith zero blockers;1with a review path means follow that log; nonzero without a path means read stderr. NEEDS_REVISION: fix blockers and re-run with--previous-run <run-id>.ESCALATED: stop same-target retries; human must narrow, split, or redesign the target.
The review updates .metareview/findings.jsonl, .metareview/runs.jsonl, docs/metareview/FINDINGS.md, and Markdown review/context artifacts.