Review-tests

One question: given this diff, are the existing tests enough to catch the bugs a careful reader would worry about?

Not whether tests exist. Not whether they pass. Just sufficiency.

Composes with /review without forking it. /review answers Standards + Spec; /review-tests answers Tests. They are siblings, not nested. See issue #50 for the add-on rationale.

Process

1. Pin the fixed point

Same as /review. Whatever the user said is the fixed point: SHA, branch, tag, main, HEAD~5. If unspecified, ask. Then capture git diff <fp>...HEAD (three-dot, against merge-base) and git log <fp>..HEAD --oneline.

If /review ran earlier in this session, surface its fixed point and confirm match before proceeding. Mismatched fixed points produce reports that look composable but aren't.

2. Identify the spec source

In order: