Skip to content

Workflow: Review and Complete PR

Run this workflow in the owning repository after a child or standalone repository-change PR is ready for final review. Invoke:

$anuva-development:anuva-review-and-complete-pr ANU-201

This page covers tracked issues. An issue-free routine or material PR is reviewed by $anuva-development:anuva-repository-change: inspect the exact head, diff, reviews, comments, review threads, and checks; stop for findings or scope growth; then ready, merge, synchronize, and clean the managed branch only after explicit merge approval. No Linear completion occurs.

Review sequence

  1. Read the normalized issue kind, Product Main contract or recorded preflight, implementation plan/log/report, and PR metadata through read-only operations.
  2. Inspect the diff and required GitHub checks.
  3. Compare implementation against issue acceptance checks and approved contracts.
  4. Run or confirm repository verification. For CMS, include relevant Playwright.
  5. Fix in-scope findings and update the implementation log/report.
  6. Strictly verify changed documentation once and provide exact links.
  7. Present the completion evidence and intended merge/status mutations.
  8. After explicit approval, mark required drafts ready. For a child, merge with anuva pr merge. For a standalone issue, use anuva repository-change complete to merge implementation first, then the optional bounded Product Main docs PR, synchronize bases, remove branches, record evidence, and mark Linear Done last.
anuva pr inspect ANU-201 --json
anuva pr checks ANU-201 --json
anuva pr ready ANU-201 --confirm
anuva pr merge ANU-201 --report C:\absolute\path\CompletionReport.md --confirm

For a standalone issue:

anuva pr ready ANU-201 --confirm
anuva repository-change docs pr ready ANU-201 --confirm
anuva repository-change complete ANU-201 --report C:\absolute\path\CompletionReport.md --confirm

Omit the docs-ready command for Not required.

The CLI must refuse merge or completion when required checks fail, the PR is not reviewable, the issue/PR link is missing, the completion report is absent, the worktree is dirty, the source branch is unmanaged, or the base branch cannot be fast-forwarded safely. Retrying the same merge command after a partial failure reconciles cleanup for already-merged PRs before completing Linear.

Cross-repository completion

An implementation issue being Done does not automatically complete the parent change. In Product Main, run the product completion review after every required repository issue is Done. Deliver the review on the completion-phase Product Main branch and PR; that merge leaves the parent In Progress. Only anuva linear change complete marks the parent Done.