القائمة
PR readiness dashboard — tracks which reviews have been completed per branch and gates merge decisions. Shows code review, tests, security, QA, and linting status.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Use when adding or reviewing tests for Reborn behavior — choosing a test tier, covering a bug fix, testing model/tool-choice behavior, touching tests/integration or tests/fixtures/llm_traces, or when a test needs Postgres, Docker, or a live LLM.
Navigate building a user-facing feature in the Reborn stack (a capability that crosses product_workflow → composition → webui_v2 → runtime/serve → frontend). Use when planning or implementing any new Reborn settings page, endpoint, facade method, or runtime-backed capability — especially before writing code, to avoid rebuilding what already exists and to wire it in one pass instead of layer-by-layer.
Use when asked to "review the open PRs", review a batch or stack of pull requests, or run a recurring PR-review pass on a repo — especially with many PRs, stacked branches, conflicts, or security-sensitive changes. Covers grouping, fan-out to review subagents, verdict synthesis, and posting.
Generate or update the IronClaw architecture overview video using Remotion. Use when asked to update, regenerate, or modify the architecture video, add/remove scenes, or reflect codebase changes in the video.
Use when writing or reviewing a change in crates/ that adds a trait, a crate, a dependency edge, a re-export, or code in ironclaw_reborn_composition — or when deciding whether an abstraction, layer, or crate boundary is justified in the IronClaw Reborn stack.
Use when starting work in the IronClaw repo, deciding where a feature/fix/prompt/doc belongs, tracing how a request flows, looking up which crate owns a subsystem, or when repo docs, the knowledge graph, or component names seem stale, missing, or contradictory.
| name | review-readiness |
| version | 0.1.0 |
| description | PR readiness dashboard — tracks which reviews have been completed per branch and gates merge decisions. Shows code review, tests, security, QA, and linting status. |
| activation | {"keywords":["review readiness","ready to merge","PR readiness","ship checklist","merge checklist","review status","PR status","can I merge","ready to ship"],"patterns":["(?i)(is|are) (this|it|PR|the PR) ready (to|for) (merge|ship|review)","(?i)(review|merge|ship) (readiness|checklist|status)","(?i)what (checks|reviews) are (missing|left|needed)"],"tags":["developer","review","process"],"max_context_tokens":1200} |
Track process completeness per PR branch. Gate merges on evidence, not gut feel.
For each active PR branch, maintain a readiness state in projects/<owner>-<repo>/readiness/<branch-slug>.md:
---
type: review-readiness
repo: owner/repo
branch: feature-branch-name
pr_number: 123
updated_at: YYYY-MM-DD
---
# Review Readiness — PR #123
| Check | Status | Last Run | Score | Notes |
|-------|--------|----------|-------|-------|
| Code review | completed | 2026-03-28 | — | Approved by @alice |
| Tests | passing | 2026-03-28 | — | CI green, 3 new tests |
| Security review | completed | 2026-03-28 | 85/100 | 1 P3 finding (accepted) |
| QA review | pending | — | — | Not yet run |
| Linting | passing | 2026-03-28 | — | Zero warnings |
## Verdict: NOT READY
Missing: QA review
## Findings log
- [2026-03-28] Security: P3 — missing rate limit on new endpoint (accepted risk)
- [2026-03-28] Code review: approved, 2 nits addressed
Checking readiness: User asks "is this PR ready?" or "can I merge?"
pending/security-review and /qa-review to complete."After running a review skill: When /security-review or /qa-review completes, update the readiness file with the result and score.
In the morning brief: For PRs that are "READY TO MERGE" (approved + CI green), also check review readiness. If security or QA is missing, note it: "READY TO MERGE (code + CI), but security review not run."
The readiness file is updated by:
/security-review runs on the branch/qa-review runs on the branchcargo clippy / eslint outputWhen presenting readiness, show dual-time estimates for remaining work:
This reframes the cost — completeness is cheap with AI assistance.