Check PR merge readiness against per-branch review and CI evidence.
npx skills add https://github.com/nearai/ironclaw --skill review-readiness-nearai
Please help me install this Agent Skill. Skill: review-readiness Source: https://github.com/nearai/ironclaw/tree/main/skills/review-readiness Command: npx skills add https://github.com/nearai/ironclaw --skill review-readiness-nearai
It prevents premature merges by giving a clear, evidence-based dashboard for whether required reviews (code, tests, security, QA, linting) are complete for each PR branch.
projects/<owner>-<repo>/readiness/<branch-slug>.md.Ask whether the pull request is ready to merge and the assistant will load or create the readiness dashboard for that branch, then report the verdict and any missing reviews.
High-intent search queries and answers about installing and using this skill.
PR merge readiness is checked by evaluating completed reviews and CI status against a per-branch readiness record. The system loads or creates a readiness dashboard for the branch and reports a merge verdict along with any missing reviews.
Tracking QA and security review checklists involves maintaining a per-branch readiness file that captures review results, scores, and unresolved findings. This record updates checklist statuses dynamically based on review outcomes and CI state.
Merge gating applies explicit verdicts to pull requests by checking checklist completion, CI status, and unresolved findings. It produces statuses like READY, ALMOST READY, NOT READY, or BLOCKED to prevent premature merges.
Morning brief readiness notes are generated by reading the per-branch readiness record and presenting a structured readiness dashboard. This dashboard provides the current merge verdict and highlights any missing code, security, or QA reviews.
Missing reviews blocking a merge are identified by evaluating the per-branch readiness checklist against completed CI evidence. The dashboard captures missing items and provides guidance on what to run next, such as a security or QA review.
PR readiness tracking does not require external dependencies. It operates by reading or creating readiness files within the project directory and updating checklist statuses based on the CI state and review outcomes you provide.
korwlik23Create structured test plans for unit, integration, and E2E testing scenarios.
LeonardoTan19Guide merge, PR, or discard decisions for completed development branches.
NixdorferAutomate multi-phase code verification with build, type, lint, test, and security checks.
bhianerdMerge eligible GitHub pull requests after CI and readiness checks, then verify deployment and canary health.