القائمة
Use when diagnosing bugs, test failures, or unexpected behavior. Requires hypotheses before fixes — no jumping to solutions.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
| name | debug |
| description | Use when diagnosing bugs, test failures, or unexpected behavior. Requires hypotheses before fixes — no jumping to solutions. |
Diagnose before you fix. Hypotheses before changes. Boring explanations before clever ones.
/verifyIf your approach fails twice, stop and reassess — you're missing context.
$ARGUMENTS
استنادا إلى تصنيف SOC المهني
Orient in project state before starting work
Review open issues and PRs across the workspace to decide what needs action
Examine evidence (files, logs, code, output) against user instructions and baseline quality factors. Audit only, no fixes.
Use when executing an implementation plan. Builds in TDD cycles with disciplined commits — one commit per plan step, no unrelated files swept in.
Use before building anything non-trivial — new features, architectural changes, multi-file modifications. Explores intent, requirements, and design before implementation.
Deploy one or more services end-to-end with health verification
