القائمة
Shape the final output to user intent — concise answer vs implementation summary vs plan vs review report vs hand-off note. Use when producing the response the user actually receives.
التثبيت باستخدام 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 | output-contract |
| description | Shape the final output to user intent — concise answer vs implementation summary vs plan vs review report vs hand-off note. Use when producing the response the user actually receives. |
The shape of the answer is part of the answer. A long essay when the user asked for a yes/no is wrong even when it is technically correct; a one-liner when the user asked for a report is wrong the same way.
The shape that matches the intent: answer · artifact · summary-of-completed-work · plan · review · hand-off. Pick one; combine only when the user asked for a combination.
