mvschwarz/openrig / packages/daemon/specs/agents/shared/skills/process/verification-before-completion
verification-before-completion
VerifiedUse when about to claim work is complete, fixed, or passing, or before committing or creating PRs
| File | Kind | Size |
|---|---|---|
| LICENSE.txt | markdown | 1.0 KB |
| SKILL.md | skill md | 6.3 KB |
| references/performance-claims.md | markdown | 1.0 KB |
references/performance-claims.md
View on GitHub# Performance claims
Read this before claiming that a change makes something faster, lighter or more responsive. It's for a performance claim, not for every change.
- Bind the claim to the versions, fixture and workload you measured.
- Count the correct work completed and the failures, as well as the time. A speedup that comes from doing less work isn't one.
- Keep the relevant setup comparable between the runs you compare, and separate what your instrumentation costs from what you measure.
- Report the repetitions and the variability, and state the limits. Choose enough repetitions to support the precision you claim; there's no fixed minimum.
- Freeze a suitable harness while you compare candidates.
- Stop when the selected outcome is met, or when the remaining experiments no longer justify their cost. An honest negative result is a result; keep it.
Adapted from the benchmark-checklist method in Cursor's pstack plugin (https://github.com/cursor/plugins/tree/190d28736eff128ec94f502a22c7fe0c4b56cd37/pstack).
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| 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 implementation | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirements | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| 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 fallback | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| 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 always | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |