Explain code

Skill viknesh20-20/claude-code-tool-kit/.claude/skills/explain-code

Production-ready Claude Code configuration. 12 original agents, 200+ slash-command skills, 45+ MCP servers, 14 plugins, design + 3D + WebGPU + GSAP + RAG tooling. One-command Node.js installer for premium websites, SaaS apps, AI agents. Free, MIT, stack-agnostic.

Install

npx -y skills add viknesh20-20/claude-code-tool-kit --skill explain-code

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

5 stars5 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Explains code with multiple levels of detail — high-level purpose, line-by-line walkthrough, data flow diagrams, and design rationale. Use when onboarding to unfamiliar code or trying to understand complex logic.

SKILL.md

2.2 KB, as published. Nobody here has run it

Code Explanation

Instructions

Step 1: Identify the Target

Read the specified file, function, or module completely. Also read:

Any imports/dependencies it uses
Any files that import/call it (to understand usage context)
Recent git history for the file: git log --oneline -10 <file>

Step 2: Provide Multi-Level Explanation

Level 1 — One-Sentence Summary

What does this code do in plain English? A non-technical person should understand this.

Level 2 — High-Level Overview

Purpose: What problem does it solve?
Inputs: What goes in? (parameters, config, env vars, external data)
Outputs: What comes out? (return values, side effects, events emitted)
Dependencies: What does it rely on?
Callers: Who uses this? In what context?

Level 3 — Detailed Walkthrough

Walk through the code section by section:

Explain the logic flow with numbered steps
Highlight non-obvious decisions ("this uses X instead of Y because...")
Note any error handling and what triggers each path
Explain any performance-sensitive sections

Level 4 — Data Flow Diagram

Create an ASCII diagram showing:

[Input] → [Processing Step 1] → [Processing Step 2] → [Output]
                ↓                       ↓
         [Side Effect 1]         [Side Effect 2]

Step 3: Highlight Key Details

Tricky Parts: Code that might confuse a new reader
Assumptions: Implicit assumptions the code makes
Edge Cases: How are boundary conditions handled?
History: Why was it written this way? (use git blame for context)

Step 4: Related Code

List the most important related files/functions that someone exploring this code should read next.

Output Style

Use clear section headers
Include code snippets with line references
Use analogies where helpful
Adjust technical depth based on the complexity of the code