milestone-review

Verifies and merges finished milestones with fresh evidence, consistency gates, and independent code review.

4|Updated Jul 11, 2026
One-click install
npx skills add https://github.com/jmgirard/cairn --skill milestone-review-jmgirard
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: milestone-review
Source: https://github.com/jmgirard/cairn/tree/main/skills/milestone-review
Command: npx skills add https://github.com/jmgirard/cairn --skill milestone-review-jmgirard

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Shipping a milestone without rigorous verification leads to unchecked acceptance criteria, stale evidence, and unreviewed code reaching the default branch. This Skill enforces a gated review workflow in cairn-tracked repositories so every milestone is verified against fresh evidence before merge. ## Core Features & Use Cases - Evidence-based verification: Re-runs every acceptance criterion and records fresh evidence in the milestone's Review section before ticking any checkbox. - Consistency gate and independent review: Runs mechanical cairn-file validation plus toolchain checks, then spawns fresh-context reviewers (diff-bug, blame-history, prior-PR-comments lenses) scaled to the milestone's surface tier. - Approval-gated merge: Presents findings for triage, obtains explicit user approval via a chip, then pushes, opens the PR, waits for green CI, and squash-merges with a merge-approval marker. - Use Case: After implementing milestone M42 in a cairn repo, run the review to verify all criteria, get an independent three-lens code review, and merge the PR only after your explicit approval. ## Quick Start Ask the assistant to review and ship milestone M42 by running /milestone-review M42 in a cairn-tracked repository.

Frequently Asked Questions about milestone-review

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I review and merge a milestone in a cairn repo?

Run /milestone-review with the milestone ID, such as /milestone-review M42. The skill verifies each acceptance criterion with fresh evidence, runs consistency gates and independent reviewers, then asks for your approval before pushing, opening the PR, and squash-merging.

What happens if an acceptance criterion fails during milestone review?

The milestone status returns to in-progress with a work-log line naming exactly what failed, and the review stops. Criteria are never reinterpreted; a wrongly written criterion goes back for a gated amendment before re-review.

Does the milestone review require GitHub and CI checks?

Yes, it pushes the branch, opens a PR with gh pr create, and waits for green CI via gh pr checks before merging. A PR with no checks can merge on local green only where the toolchain profile declares the repo CI-less.

Can I merge a milestone without user approval?

No. The merge authorization is presented as an explicit approval chip, and a PreToolUse hook denies merges to the default branch without a written approval marker naming the specific PR. Declining returns the milestone to in-progress.

What is the thrash rule in milestone review?

The thrash rule counts defect returns per milestone in the work log. At the third return, the recommended remedy is descope-or-park rather than another retry, and repeated same-shape failures trigger reconsideration of the recorded alternative or escalation.