ctx-explain
Explain code for someone new to the project. Use when the user asks 'what does this do', 'explain this', or wants to understand unfamiliar code.
Best use case
ctx-explain is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Explain code for someone new to the project. Use when the user asks 'what does this do', 'explain this', or wants to understand unfamiliar code.
Teams using ctx-explain should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/ctx-explain/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How ctx-explain Compares
| Feature / Agent | ctx-explain | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Explain code for someone new to the project. Use when the user asks 'what does this do', 'explain this', or wants to understand unfamiliar code.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
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. 1. **What it does**: Describe the purpose and behavior in plain language. 2. **Why it exists**: What problem does it solve? What would break without it? 3. **How it connects**: Which modules call it, and which modules does it depend on? 4. **Key design decisions**: Why was this approach chosen over alternatives? 5. **Non-obvious details**: Anything surprising, subtle, or easy to misunderstand. ## Execution 1. Read the target code 2. Read `.context/ARCHITECTURE.md` for system-level context 3. Trace callers and callees if connections matter 4. 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."
Related Skills
ctx-verify
Verify before claiming completion. Use before saying work is done, tests pass, or builds succeed.
ctx-skill-creator
Create, improve, test, and deploy skills. Full skill lifecycle from intent to working skill file.
ctx-sanitize-permissions
Audit tool permissions for dangerous or overly broad entries. Use to ensure safe agent configuration.
ctx-recall
Browse session history. Use when referencing past discussions or finding context from previous work.
ctx-prompt
Apply, list, and manage saved prompt templates from .context/prompts/. Use when the user asks to apply, list, or create a reusable template like code-review or refactor.
ctx-journal-normalize
Normalize journal source markdown for clean rendering. Use after journal site shows rendering issues: fence nesting, metadata formatting, broken lists.
ctx-import-plans
Import plan files into project specs directory. Use to convert external plans into project-tracked specs.
ctx-compact
Archive completed tasks and trim context. Use when context files are growing large.
ctx-check-links
Audit docs for dead links. Use before releases, after restructuring docs, or when running a documentation audit.
ctx-add-task
Add a task. Use when follow-up work is identified or when breaking down complex work into subtasks.
ctx-add-learning
Record a learning. Use when discovering gotchas, bugs, or unexpected behavior that future sessions should know about.
ctx-add-decision
Record architectural decision. Use when a trade-off is resolved or a non-obvious design choice is made that future sessions need to know.