Code Walkthrough
Interactive step-by-step code walkthrough for entire codebases (single or multi-file). Explains each section's logic, assumptions, and data transformations, then RUNS the code and shows actual output - dataframe dimensions, head(), model summaries, plot descriptions, file previews. Pauses after each section for questions. Use whenever the user says "walk through", "explain", "go through", "break down", "review", "understand", "what does this code do", "help me understand this script", "annotate", "explain step by step", or "walk me through the codebase". Also trigger if someone just points at
Install
npx skills add dariia-m/my_claude_skills --skill code-walkthroughgit clone --depth 1 https://github.com/dariia-m/my_claude_skills.git /tmp/my_claude_skills
mkdir -p ~/.claude/skills
cp -r /tmp/my_claude_skills/code-walkthrough ~/.claude/skills/code-walkthroughPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Code Walkthrough Skill You are conducting an interactive, thorough code walkthrough of an entire codebase. Your job is to be the most patient, detailed teacher imaginable. You leave nothing unexplained. And you do not just *describe* what the code does - you *run it* and show what it actually produces. ## Core Philosophy Every line of code makes decisions. Some are obvious, some are buried. Your job is to surface ALL of them. A junior researcher or someone inheriting this code should, after your walkthrough, understand not just *what* the code does but *why it works the way it does* and *what would break if the assumptions were wrong*. Do not summarize. Do not gloss over "obvious" things. What is obvious to one person is a mystery to another. If the code loads a library, explain what that library does and why it is needed here. If the code sets a seed, explain what reproducibility means in this context. **The output rule**: For every code section, you must show what it produces. If the code prints something, show the print output. If it creates a dataset, show `dim()`, `head()`, `str()`, or `summary()` as appropriate. If it produces a plot, describe what the plot shows or save/display it. If it fits a model, show the model summary. If it writes a file, confirm the file was written and show its size or a preview. The user should never have to wonder "but what does this actually look like in practice?" ## Walkthrough Procedure ### Step 0: Codebase Discovery
Details
- Skill name
code-walkthrough- Repository
- dariia-m/my_claude_skills
- Path
code-walkthrough/SKILL.md- License
- MIT
- Repo updated
- 16 November 2026
FAQ
What does the Code Walkthrough skill do?
Interactive step-by-step code walkthrough for entire codebases (single or multi-file). Explains each section's logic, assumptions, and data transformations, then RUNS the code and shows actual output - dataframe dimensions, head(), model summaries, plot descriptions, file previews. Pauses after each section for questions. Use whenever the user says "walk through", "explain", "go through", "break down", "review", "understand", "what does this code do", "help me understand this script", "annotate", "explain step by step", or "walk me through the codebase". Also trigger if someone just points at
How do I install the Code Walkthrough skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add dariia-m/my_claude_skills --skill code-walkthrough. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Code Walkthrough popular?
It lives in dariia-m/my_claude_skills, which has 36 GitHub stars and 11 forks.
Related skills
Academic Paper Verify
36dariia-m/my_claude_skills
Thoroughly verify all code, tables, figures, modeling decisions, and quantitative claims in an academic paper against its source R scripts and output files. Use this skill whenever you need to audit, replicate, or verify an academic research paper - including cross-checking LaTeX tables against R output, validating econometric modeling choices, ensuring sample sizes are consistent, building a verification manifest, and running automated replication tests. Trigger this skill for any mention of: paper verification, replication check, table audit, code-paper consistency, reproducing results, veri
Academic Writing
36dariia-m/my_claude_skills
Activate when the user is drafting any academic economics content from scratch (e.g., outlines, abstracts, introductions, data/methods/identification sections, results narratives, conclusions, referee responses, table/figure captions) and needs economics-specific structure, phrasing options, and quality checks to produce publication-ready prose.
Anti Hallucination
36dariia-m/my_claude_skills
ALWAYS activate this skill. Apply these rules to every task regardless of domain. This skill governs how Claude Code verifies information, writes code, references documentation, and avoids fabricating functions, arguments, APIs, file paths, data structures, or facts. These rules override any inclination to guess.
Commenting Intent
43obra/clank
Comment WHY code exists and non-obvious decisions, not WHAT code does (mechanics)
Code Quality
38sam-dumont/claude-skills
Automatically triggered when setting up Python code quality tooling, configuring linters, adding type checking, improving code standards, running code quality checks, setting up pre-commit hooks, or auditing Python code for quality issues. Applies when discussing: ruff setup, mypy configuration, code formatting, linting rules, cyclomatic complexity, dead code detection, file length limits, pre-commit hooks, Makefile targets for quality, uv-based workflows, pyproject.toml configuration, or "check my code quality". Also triggers on: "set up linting", "add type checking", "configure ruff", "forma
Debug to Fix
62ElliotJLT/Claude-Skill-Potions
When debugging frustration appears ("why isn't this working?", "it should work", "I don't understand"), orchestrate the full debug cycle: clarify → investigate → fix → verify. Prevents the common failure of jumping to fixes before understanding the problem. An elixir that chains rubber-duck and prove-it with investigation.
Browse the most popular Claude skills, all software development skills, or write your own with the skills generator.