بنقرة واحدة
review
Run evaluator and security reviewer concurrently for comprehensive quality gate.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
القائمة
Run evaluator and security reviewer concurrently for comprehensive quality gate.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Autonomous build loop with Karpathy ratcheting, GAN evaluator, and session chaining. Iterates story groups until all features pass or stopping criteria met.
Socratic interview to create a Business Requirements Document. First step in the SDLC pipeline.
Generate system architecture, machine-readable schemas, and UI mockups. Spawns planner + ui-designer concurrently.
Evaluation patterns — sprint contract format, three-layer verification, scoring rubric references.
Standard GitHub issue workflow. Branch, reproduce, fix, test, PR.
Generate production code and tests for a story group using agent teams for parallel execution.
| name | review |
| description | Run evaluator and security reviewer concurrently for comprehensive quality gate. |
| argument-hint | [story-id] |
| context | fork |
Run a comprehensive quality gate by spawning the evaluator and security reviewer as concurrent agents. Both must pass before the group is considered ready for merge.
/review
/review E3-S1
With no argument: reviews the current group in context. With a story ID: reviews the specific story and its group.
Use the Agent tool to spawn both agents at the same time in a single call. Do not run them sequentially — concurrent execution is the point of this skill.
Agent 1 — evaluator
specs/reviews/evaluator-report.md.features.json with pass/fail verdicts.Agent 2 — security-reviewer
specs/reviews/security-review.md.Both agents run against the same set of changed files and the same group context.
| Level | Meaning | Action Required |
|---|---|---|
| BLOCK | Must be fixed before merge | Self-healing loop |
| WARN | Should be fixed; does not block | Log and track |
| INFO | Optional improvement | No action required |
Do not treat WARN as BLOCK. Do not treat INFO as WARN. The severity assigned by the reviewer is final unless the reviewer is re-run after a fix.
If either agent reports one or more BLOCK findings:
generator agent with:
/review cycle (both agents concurrently).Do not merge or mark a group complete while any BLOCK finding remains open.
| Mode | Evaluator | Security Reviewer |
|---|---|---|
| Full | Run | Run |
| Lean | Run | Run |
| Solo | Skip | Run |
In Solo mode, only the security-reviewer runs. The evaluator is skipped because there is no running application stack. Print a note: "Solo mode: evaluator skipped, security review only."
After both agents complete (or in Solo mode, after the security reviewer completes):
specs/reviews/evaluator-report.md — overall PASS/FAIL verdict with per-check detail.specs/reviews/security-review.md — list of BLOCK/WARN/INFO findings with file references.Both files must exist before the review cycle is considered complete. If either agent fails to produce its output file, treat that as a BLOCK finding.