القائمة
Use when about to claim work is complete, fixed, or passing — requires running verification commands and confirming output before making any success claims
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
Use when a structured PRD document is needed for the ralph loop — generates prd.json and progress.txt
Use when task scope exceeds one context window and decomposes into independent pass/fail stories with clean iteration boundaries
Use when implementation is complete, all tests pass, and you need to decide how to integrate the work — merge, PR, or cleanup
Use when starting feature work that needs isolation from the current workspace or before executing plans that could leave the branch in a broken state
Use when a hard problem was just solved and the solution should be captured as a learning for future reference
Use when 3+ distinct occurrences suggest a skill should be updated with a new trigger, anti-pattern, or verification step
استنادا إلى تصنيف SOC المهني
| name | verification-before-completion |
| description | Use when about to claim work is complete, fixed, or passing — requires running verification commands and confirming output before making any success claims |
| tags | ["gate","verification","quality"] |
| triggers | ["done","complete","fixed","passing","ready","finished","works now"] |
| chains_to | ["self-review"] |
| priority | gate |
| gate | true |
Before claiming ANYTHING is done: run the verification commands, read the output, confirm success. Evidence before assertions. Always.
Based on the project and the work done, determine the right verification:
| Work Type | Commands |
|---|---|
| Rust code | cargo build --workspace, cargo clippy --workspace -- -D warnings, cargo test --workspace, cargo fmt --all -- --check |
| TypeScript | npm run build, npm run lint, npm run test |
| Python | python -m pytest, mypy ., ruff check . |
| Any code | Project-specific commands from CLAUDE.md |
| Bug fix | The exact reproduction steps that demonstrated the bug |
| Config | Restart/reload and verify the change took effect |
Always check the project's CLAUDE.md for project-specific verification commands.
Run each verification command. Do not skip any.
Read ALL output. Not just the exit code. Look for:
syntaxninja-dojo:self-review.| Anti-Pattern | Why It's Wrong |
|---|---|
| "Tests should pass" | Run them. Know they pass. |
| "I didn't change anything that would break tests" | Butterfly effect. Run them. |
| "The build succeeded so it's fine" | Build != lint != test != format. Run all. |
| Claiming "fixed" after editing but before verifying | The edit might have introduced new issues. |
| Skipping verification for "trivial" changes | Trivial changes cause production incidents. |
Evidence before assertions. Always.
If you cannot run verification commands (no test suite, no build), explicitly state: "I cannot verify this because [reason]. Here's what I'd check: [list]."
REQUIRED: syntaxninja-dojo:self-review (after verification passes)