القائمة
Review a ticket/issue for engineering readiness — completeness, clarity, blockers. Triggers: "review this ticket/issue", "is this ready", "can engineering start".
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Design/spec a new feature, component, or behavior change before any code. Triggers: "how should we…", "what's the best way", "let's build/add/create", "design", "plan", "spec". Outputs an approved spec → hands off to worker.
Implement code from a spec or requirement — plan, small steps, evidence-verified. Triggers: "build", "implement", "fix", "work on", "let's start", or any multi-step change after a spec.
Ultra-terse caveman replies — drops articles, filler, hedging, pleasantries. Keeps all technical content.
Root-cause a bug before fixing — reproduce, evidence, single hypothesis, minimal test. Use for any bug, test failure, build break, or unexpected behavior — especially when a "quick fix" feels obvious.
Simplify recently changed files — remove dead code, clearer names, less nesting — without behavior change. Triggers: "/polish", "clean up", "simplify", "tidy".
Design/spec a new feature, component, or behavior change before any code. Triggers: "how should we…", "what's the best way", "let's build/add/create", "design", "plan", "spec". Outputs an approved spec → hands off to worker.
| name | ticket-review |
| description | Review a ticket/issue for engineering readiness — completeness, clarity, blockers. Triggers: "review this ticket/issue", "is this ready", "can engineering start". |
Review tickets as written, not as you imagine them. Identify blockers, ambiguities, and risks for an engineer who would start work today. Do not rewrite the ticket or post comments unless explicitly asked.
A ticket is ready when it has:
Bugs also need: actual vs expected, repro steps, environment, frequency, impact, evidence (logs/screenshots/IDs).
Features/stories also need (when relevant): actor/persona, business outcome, UX refs, API/data contracts, permissions, analytics, localization, accessibility, rollout/migration.
Don't overuse Blocker. If a reasonable decision is possible from existing patterns, downgrade.
Pastable as a Jira comment. Skip sections that add nothing.
## Ticket Intent
<1–2 lines>
## Review
**[Severity]** Short issue title
Explanation: what's missing or unclear, and why it matters.
Question: the exact question to ask PM or ticket owner.
## Concrete Improvements
- <ready-to-copy improvement>
## Summary / Verdict
<Ready: why it's good enough, OR Needs Changes: concise list of blockers/gaps>
If there are no meaningful gaps, keep it short and mark Ready.