القائمة
Write a Conventional Commits message describing a code change. Use when the goal mentions creating a commit, writing commit message, or committing changes.
التثبيت باستخدام 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.
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.
Coordinate multi-persona work with a shared blackboard, role boundaries, hand-off contract, conflict resolution, and final synthesis. Use when a task benefits from more than one persona.
| name | git-commit-message |
| description | Write a Conventional Commits message describing a code change. Use when the goal mentions creating a commit, writing commit message, or committing changes. |
Write commit messages that explain why, not what. The diff already shows what.
git commit and need to draft the -m text.type(scope): short imperative summary (≤72 chars)
(optional body — wrap at 72 chars)
- Why this change is needed
- Constraints or trade-offs the reader should know about
- Anything surprising in the implementation
Refs: #123
feat — new user-facing capabilityfix — bug fix; pair with a regression testrefactor — internal restructure, no behavior changedocs — comments / README / docs onlytest — tests onlychore — tooling, deps, CIperf — performance change with measurable impactgit diff --staged. Don't write from memory.fix(workflow): reset retry counter when step succeeds
Counter was sticky — a retried step that finally succeeded still
counted toward the `maxAttempts` budget for siblings. Reset on
success so failure quotas are per-step, not per-workflow.
refactor(skill-cards): extract envelope renderer
No behavior change. Pulls the `<skill-card hash="...">` rendering
out of the prompt-section so future card sources (autonomous,
imported) can reuse the same envelope.