Skill

ctx-explain

From ctx

Explains code for project newcomers with structured coverage of purpose, rationale, connections, design decisions, and non-obvious details. Use for 'explain this', 'what does this do', or onboarding.

developer-tools

npx claudepluginhub activememory/ctx --plugin ctx

Tool Access

This skill is limited to using the following tools:

ReadGrepGlob

Preview

Explain the specified code for someone new to the project. Tailor

SKILL.md

Similar Skills

codex-explain

147

Explains complex code via Codex MCP, tracing logic, data flow, and key concepts. For onboarding unfamiliar code or understanding execution. Structured output at brief/normal/deep depths.

1 file5 tools

sd0x-dev-flow

explain

Explains complex code, files, directories, or concepts by routing to expert agents, using structural search and code stats, and generating mermaid diagrams for architecture and data flow.

1 tool

claude-mods

explain

129

Explains code, concepts, and technical decisions in clear, structured terms by gathering context from files, tests, comments, and git history.

4 tools

core

Stats

Parent Repo Stars41

Parent Repo Forks9

Last CommitMar 28, 2026

Actions

View Source View Plugin View on GitHub View README

Help us improve

Share bugs, ideas, or general feedback.

Explain the specified code for someone new to the project. Tailor depth to the user's expertise if known from context.

When to Use

User says "explain this code", "explain this", "what does this do"
User is onboarding to an unfamiliar area of the codebase
User says "walk me through this" or "how does this work"

When NOT to Use

User wants deep architectural analysis (use /ctx-architecture)
User wants to trace a bug (use /gitnexus-debugging)
User wants execution flow tracing (use /gitnexus-exploring)

Explanation Structure

Cover each dimension in order. Skip any that don't apply.

What it does: Describe the purpose and behavior in plain language.
Why it exists: What problem does it solve? What would break without it?
How it connects: Which modules call it, and which modules does it depend on?
Key design decisions: Why was this approach chosen over alternatives?
Non-obvious details: Anything surprising, subtle, or easy to misunderstand.

Execution

Read the target code
Read .context/ARCHITECTURE.md for system-level context
Trace callers and callees if connections matter
Present the explanation following the structure above

Keep it concise. Lead with the "what": the reader wants to orient before diving into "why" and "how."