القائمة
Use when handling review feedback so responses are technical, verified, and implementation actions are sequenced safely.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
Use when writing technical articles, blog posts, X/Twitter threads, LinkedIn posts, documentation, runbooks, or any text that must sound like a specific person, not a generic assistant. Also use when the user asks to humanize text, remove AI-sounding language, rewrite in their voice, or convert rough notes into publishable content. Trigger even when the user just says "write this up" or "draft a post about X" without explicitly mentioning voice or tone.
Use when reviewing architecture, planning refactors, reducing coupling, improving testability, or deciding whether modules should become deeper behind simpler interfaces.
Use when the user asks for caveman mode, terse mode, fewer tokens, less prose, or very brief technical communication.
Use for hard bugs, failing checks, pipeline failures, homelab incidents, performance regressions, or reports that something is broken and needs root-cause analysis.
Use before git mutation, branch deletion, resets, cleaning, force pushes, broad restore commands, PR operations, or any git action with destructive or remote side effects.
Use when a plan, design, or implementation request has ambiguity that could change scope, architecture, acceptance criteria, safety, or validation.
استنادا إلى تصنيف SOC المهني
| name | receiving-code-review |
| description | Use when handling review feedback so responses are technical, verified, and implementation actions are sequenced safely. |
Treat feedback as technical input to verify, not performative agreement to repeat.
Push back with technical evidence when a suggestion:
Return:
Clarifications: questions that must be resolved first, or none.Accepted items: fixes implemented.Rejected items: technical reason for disagreement.Validation: commands run and outcomes.