SkillValidated

Verify-after-accept — close the loop on accepted changes

A skill that runs after you accept a change: it re-derives what the change claims to do, runs the narrowest real check that could falsify it, and reports what remains unverified — so acceptance and verification stop drifting apart.

$cosq add verify-after-accept

Free, works signed out. No CLI? Copy the file below into your repo — same result.

Why this one

Developers measurably overestimate AI-assisted speed and skip verification (METR RCT) — a check that runs right after acceptance closes that gap.

How to use it

  1. 1Invoke right after accepting a non-trivial change
  2. 2Treat 'unverified' as an action item, not a footnote

What gets installed

Pick your tool to preview the exact file cosq add writes — byte-for-byte. Prefer copy-paste? Use the copy button on the file.

.claude/skills/verify-after-accept/SKILL.md(created)
---
name: verify-after-accept
description: Use immediately after accepting a code change: run the narrowest real check that could falsify it and report what remains unverified.
---

After a change is accepted, verify it before anything else builds on it:

1. State, in one line, what the change claims to do.
2. Find the narrowest REAL check that could falsify that claim: the scoped
   test, the type check, running the affected command or page.
3. Run it. Report the actual result — never infer success from the code
   looking right.
4. List what remains unverified (untested branches, mocked dependencies,
   assumptions about inputs) and the single cheapest check that would cover
   the riskiest one.

If nothing runnable covers the change, say exactly that, and propose the one
test worth adding before continuing.