القائمة
Decide the verification tier — typecheck, lint, affected tests, full suite, manual check. Use when finishing a change, reviewing one, or planning what evidence will prove the work.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Review code changes for correctness, error handling, scope creep, and style. Use when the goal mentions reviewing a PR, diff, or file.
Walk through a stack trace or error log to find the root cause. Use when the goal mentions debugging, investigating an error, or tracking down a bug.
Write a Conventional Commits message describing a code change. Use when the goal mentions creating a commit, writing commit message, or committing changes.
Outline unit tests for a function or module before writing them. Use when the goal mentions writing tests, test plan, or test coverage.
Keep effort proportional to risk — prefer the cheapest sufficient workflow, escalate only on evidence, refuse over-analysis on simple tasks. Use when choosing depth, level, or workflow shape.
Map required capabilities to persona roles and available skills. Detect missing skill coverage and decide whether to acquire a skill, request one, or proceed generically. Use when scoping a workflow.
| name | verification-strategy |
| description | Decide the verification tier — typecheck, lint, affected tests, full suite, manual check. Use when finishing a change, reviewing one, or planning what evidence will prove the work. |
Verification proportional to risk. Over-verifying small changes wastes time; under-verifying risky ones loses trust. The strategy is decided up front and matched at the end.
A short verification note: tier · what it covers · what it does not cover · residual risk. Attach to the artifact so a reviewer sees what was actually checked.
