skills.rest
zeropoint-foundation
zeropoint-foundationCOMMUNITY
Explore all skills by this author →
GitHub

review-readiness

Aggregates code review, tests, security, QA, and linting statuses per branch to determine readiness.

1|Updated May 11, 2026
Search Tags:#security#qa#pr#code-review#ci#pull-request#review-readiness
One-click install
npx skills add https://github.com/zeropoint-foundation/ironclaw --skill review-readiness-zeropoint-foundation
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: review-readiness
Source: https://github.com/zeropoint-foundation/ironclaw/tree/main/skills/review-readiness
Command: npx skills add https://github.com/zeropoint-foundation/ironclaw --skill review-readiness-zeropoint-foundation

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Keeps PRs moving by surfacing readiness gaps across code review, tests, security, QA, and linting, so teams can focus on unresolved blockers rather than status unknowns.

Core Features & Use Cases

  • Real-time readiness dashboard per branch showing the status of code review, tests, security review, QA, and linting.
  • Automated verdicts (READY, NOT READY, BLOCKED) based on configurable criteria and evidence.
  • Change tracking with per-branch update timestamps to support governance and auditing.
  • Use Case: A developer opens a PR, the dashboard aggregates all checks, and the team gates merging until all checks are satisfied.

Quick Start

Create or open a readiness dashboard for a specific PR branch and start tracking its reviews, CI, and linting status.

Frequently Asked Questions about review-readiness

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

FAQPage Schema
How do I track pull request readiness across code review, tests, and security checks?▼

Track pull request readiness by aggregating code review, tests, security, QA, and linting statuses per branch into a dashboard. This surfaces unresolved blockers and presents a clear verdict on whether a PR is ready to merge.

How does automated PR gating work for branch-level CI and linting statuses?▼

Automated PR gating works by enforcing configurable criteria against aggregated evidence from CI and linting statuses. It automatically generates a READY, NOT READY, or BLOCKED verdict to prevent merging until all checks are satisfied.

Can I use a readiness dashboard to gate merges for active pull requests across repositories?▼

Yes, you can use a readiness dashboard to gate merges for active pull requests across repositories. It updates statuses per branch as reviews occur and CI results change, enforcing gating rules for each PR.

What is the best way to surface code review and QA blockers before merging a branch?▼

The best way to surface code review and QA blockers is to aggregate all check statuses per branch into a real-time dashboard. This highlights readiness gaps so teams can focus on unresolved blockers rather than status unknowns.

Does tracking PR readiness store updated timestamps for governance and auditing?▼

Yes, tracking PR readiness stores per-branch update timestamps as statuses change. This change tracking supports governance and auditing requirements by recording when reviews and CI results were last updated.

Related Skills

Explore More Software Engineering Skills→
daodaoedudaodaoedu

collect-pr-feedback

Collect and consolidate GitHub pull request feedback and CI check statuses.

Official
Intermediate
mr-daedaliummr-daedalium
107

land-and-deploy

Merge PRs, trigger deployment, and verify canary health in CI/CD pipelines.

Community
Advanced
philo-grovesphilo-groves
12

maxtac-sast-control-flow-graph

Construct static analysis graphs for reachability, guard dominance, and path feasibility.

Community
Advanced
awinogradovawinogradov
5

pr:monitor

Monitor pull requests for review approval and CI check status.

Community
Intermediate