← ClaudeAtlas

ready-reviewlisted

Review gate before a draft PR is flipped to ready. Use when the user asks to mark a PR ready, asks for the pre-ready review, or the PR flow reaches that step. Three read-only reviews run in parallel (defects, standards, spec), then one fix agent commits every finding it cannot refute with evidence; only open questions come back to the user.
SummerRiversound/awesome-claude-harness · ★ 0 · Code & Development · score 72
Install: claude install-skill SummerRiversound/awesome-claude-harness
# Ready review A draft PR is flipped to ready only through this gate. The human reviewer sees a finished result, not a list of findings to act on. The review agents carry the coding standards; the implementation context does not need to. ## 1. Preconditions (main session) - Working tree clean, every change committed on the PR branch. - Fresh base: `git fetch`. When HEAD does not contain `origin/$base` (or, for a stacked PR, the default branch the base should already hold), rebase first; decisions merged in between are part of the review. Review the lower PR of a stack before the upper one, then rebase the upper. - Fixed point: `base=$(gh pr view --json baseRefName -q .baseRefName)`, then `git merge-base origin/$base HEAD`. The diff under review is `git diff <merge-base>...HEAD`. - Spec source, first found wins: the linked issue (`gh pr view --json closingIssuesReferences`), a spec file the repo keeps for this feature, the PR body's Summary. - Standards sources: every agent instruction file the repo has (`AGENTS.md`, `CLAUDE.md`, `.github/copilot-instructions.md`, `CONTRIBUTING.md`, `docs/design-system/` when present), plus the repo's decision record when it has one (`docs/DECISIONS.md` and the ADRs under `docs/ADR/` whose topic the diff touches). A change that contradicts an accepted ADR is a finding. - Layer 1 first: run the repo's own check scripts (lint, type-check, unit tests). A failure is implementation work, not review: fix, commit, then start. - If project memory h