القائمة
Fixture discipline skill with a marker but NO sibling TESTS.md. The harness must exit 2 (setup error) because there is no scenario to dispatch.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
When --quality-locked is active, loop review/revise at each Quality Gate until findings reach a clean bar (no Critical, no Major, only cosmetic Minor) or the iteration cap (10) is reached. Uses a deterministic Python checker for classification and decision logic; agent runs the actual review and revision steps.
Use after implementation passes the quality gates, when a change needs an independent pass over the code before it ships, or when the user asks to "QA this", "check the implementation", or "verify it matches the spec". Applies to Standard and Comprehensive scopes with the Task tool available; Lightweight tasks skip.
Use when the user picks [A] Review at a spec/plan/ADR/root-cause/fix-plan checkpoint, or asks for an independent review before implementation begins. Applies to Standard and Comprehensive scopes with the Task tool available; Lightweight tasks skip.
Use as the code-quality gate after spec-compliance and constitution checks pass, or when the user says "review my code", "quality check", "security review", or "is this code good". Runs as an independent sub-agent when the Task tool is available.
Adversarial review verifying implementation matches its specification — checks completeness (nothing missing) and precision (nothing extra). Distrusts the implementer's self-report. Use after implementation, or when the user says "check against spec", "does this match requirements", or "verify the implementation".
Configure Sage preset and project settings. Switch between base, startup, enterprise, or opensource constitution presets. Use when the user says "configure sage", "change preset", or "sage settings".
| name | skill-no-tests |
| description | Fixture discipline skill with a marker but NO sibling TESTS.md. The harness must exit 2 (setup error) because there is no scenario to dispatch. |
| version | 1.0.0 |
| modes | ["build"] |
| skill_type | discipline |
| compliance_marker | ⚡ Running spec review (sub-agent)... |
A discipline skill missing its TESTS.md. The harness cannot run without a scenario, so it must exit 2 rather than fabricate one.
| The excuse (observed) | Why it's wrong | The rule |
|---|---|---|
| "fixture" | n/a | n/a |
