checking-merge-readiness

Installation
SKILL.md

Checking Merge Readiness

Review a pull request before the owner merges it. Judge the full arc from pre-review intent through the current tip (design health, intent drift, redesign pressure, and follow-up debt), not a recap of individual review comments. Babysit, bot rounds, and point fixes clear the queue; ask whether the accumulated change is still the right system to put on main.

Print a short Minto pyramid brief (step 6): merge, debug, or do not merge, then wait for a numbered reply.

Thin checks run first: whether the review loop is quiet enough to grade and whether host merge rules pass (for example required conversation resolution). They never replace the whole-change review. Tip residual is residual language at most, not a skill-invented hard stop, unless a host rule requires re-approval after the last push.

Installs
17
GitHub Stars
15
First Seen
Aug 19, 2026