القائمة
Explains code with analogies and visual diagrams. Use when the user asks how code works, wants to understand a codebase, or uses phrases like "explain", "how does this work", "walk me through".
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Audits agents, prompts, skills, knowledge, and documentation for gaps, inconsistencies, and improvement opportunities. Proposes changes for user approval. Triggers on "agent-audit", "audit agents", "review config", "what can we improve".
Use before any creative work or spec creation. Explores intent, challenges assumptions, and produces specs. Triggers on "brainstorm", "let's design", "spec out", "define requirements", "write a spec", "challenge this", "poke holes", "what am I missing".
Detects documentation drift after structural changes. Dispatches parallel specialist reviewers and auto-fixes. Triggers on "check my docs", "audit docs", "doc drift", "check doc drift", or auto from post-implementation when tracked categories change.
Automated post-implementation workflow. Triggers when the orchestrator receives DONE from an implementation subagent. Runs quality gate, doc staleness check, auto-review, and improvement capture.
Periodic codebase health check. Use when the user says "health check", "technical debt", "what needs attention", "codebase audit", "codebase health".
Takes a spec phase and generates an execution plan with parallel stages, agent routing, review gates, and verification criteria. Use before dispatching implementation work. Triggers on "plan execution", "generate execution plan", "how should we execute this", or internally when the orchestrator is about to implement a spec phase.
| name | explain-code |
| description | Explains code with analogies and visual diagrams. Use when the user asks how code works, wants to understand a codebase, or uses phrases like "explain", "how does this work", "walk me through". |
When explaining code, always structure the response in this order:
State what the code does in plain English — no jargon.
Compare it to something from everyday life. Make it concrete and relatable.
Draw the flow, structure, or relationships visually. Examples:
[Input] → [Transform] → [Output]
┌──────────┐ ┌──────────┐
│ Module A │────▶│ Module B │
└──────────┘ └──────────┘
Trace through the code as if it were executing. Reference specific line numbers when pointing to important parts.
Call out one common mistake, misconception, or edge case that trips people up with this code.
Keep the tone conversational. For very complex concepts, use two analogies — one simple, one more technical. Prioritise clarity over completeness.