Checking Merge Readiness

Review a pull request before the owner merges it. The main job is to 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. Local optimizers (babysit, bot rounds, point fixes) clear the queue; this skill asks whether the accumulated change is still the right system to put on main.

Print a short Minto pyramid brief for the merge decision (shape in step 6). Recommendations are merge, debug, or do not merge. After the brief, wait for a numbered reply from whoever is talking.

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.