explain-my-codelisted

This skill should be used when the user asks to "document this codebase", "explain my code", "generate architecture docs", "write an onboarding doc", "analyze this repo", or wants self-contained technical documentation produced from source. Signal tokens include "codebase", "repo", "architecture diagram", "onboarding", "system overview", "tech stack", ".md doc". Casual phrasings (when paired with an onboarding/documentation intent) include "help a new dev understand this whole codebase", "write up how this project works", "map out this code into a doc". Also trigger when the user points at a repository and asks for a single Markdown write-up with Mermaid diagrams. Do NOT use for a quick one-line "what does this do" answer, for line-by-line code review or bug-finding (that is wordpress-architect-review or a review skill), for refactoring or modernization plans (that is refactoring-analyst), or for producing diagrams alone (that is codebase-to-mermaid).
chrismccoy/skills · ★ 2 · Web & Frontend · score 66

Install: claude install-skill chrismccoy/skills

# Explain My Code Analyze a complete code repository as a senior software architect and produce one self-contained, production-grade Markdown document that lets anyone new to the project fully understand the system with no handover meetings or outside help. ## When to Use - User asks to document, explain, or map a codebase or repository - User wants an onboarding document for people new to the project - User wants a system/architecture overview with Mermaid diagrams - User points at a repo and asks "what does this do / how does it work" AND wants it captured as a written document, not a one-line reply Do NOT use for bug-finding code review, refactoring plans, or diagram-only output (see negative boundary in description). ## Co-Load Precedence When co-loading with codebase-to-mermaid: that skill owns standalone diagram generation; this skill embeds diagrams inside the full document. When co-loading with refactoring-analyst: that skill owns refactor planning; this skill only describes the system (Section 13 suggests improvements at a high level, it does not plan the refactor). When co-loading with a code-review skill (e.g. wordpress-architect-review): review owns defect findings; this skill owns architecture explanation (Section 12 lists observations/risks but does not perform line-level review). ## Workflow ### Phase 1: SCOPE THE TARGET 1. Determine the repository root. Default to the current working directory. If the user named a path, use that. 2. If no code is pres