agentleFS
PradnyeshpPradnyeshp/Claude-Skills/.claude/skills/explain/SKILL.md

explain

Skill2 starsChanged 4 months agoMITView on GitHub

Explain a file, function, or recent diff in plain language — what it does, how it flows, and why. Use when the user asks to explain code, says "what does this do", "walk me through this file", "help me understand this", "explain the diff", or is onboarding to unfamiliar code.

129 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use debug-fix, root-cause and 8 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • zebbernSkill

    debug-fix

    Find and fix a bug or issue — from any source (GitHub issue, error message, user report, or observed behavior)

    Also in 3 projects that use this

  • Ingramradical235Skill

    root-cause

    Structured root cause analysis using WHERE (MECE decomposition) then WHY (causal structure diagrams) pipeline. Includes coin-flip detection, logical-leap detection, and vicious cycle intervention. Use when buffer enters YELLOW/RED, when metrics stall, or when Actions execute but don't produce results.

    Also in 5 projects that use this

  • neurofooSkill

    socratic

    Socratic questioning to examine beliefs, uncover assumptions, and develop deeper understanding. Use to challenge thinking, evaluate proposals, or teach without lecturing.

    Also in 4 projects that use this

  • anombyte93Skill

    discover

    Phase 1 of the prd-taskmaster pipeline: brainstorm-driven discovery. Delegates to superpowers:brainstorming in Interactive Mode (one adaptive question at a time), or self-brainstorms in Autonomous Mode when no user is present. Intercepts before the brainstorming chain hands off to writing-plans — this skill owns the exit. Extracts constraints, calibrates scale (Solo / Team / Enterprise), and advances the pipeline to GENERATE.

    Also in 6 projects that use this

  • mitsuhikoSkill

    summarize

    Fetch a URL or convert a local file (PDF/DOCX/HTML/etc.) into Markdown using `uvx markitdown`, optionally it can summarize

    Also in 8 projects that use this

  • abdullah1854Skill

    pr-summary

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

4 rules. 0 are common, 4 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 117 edited versions we read keep these.

  • 4

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Call out anything non-obvious or surprising — implicit assumptions, edge-case handling, performance characteristics, or footguns.

    line 26
  2. Distinctive:

    If the code looks buggy or fragile, note it briefly at the end, but don't turn this into a full review.

    line 27
  3. Distinctive:

    Use short paragraphs and bullet points.

    line 33
  4. Distinctive:

    Do not modify any files — this skill is read-only.

    line 34

“Common” is measured: kept by at least 6 in 10 of the 117 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Recent diff (used when the user asks to explain "the diff" or "the changes")

!git diff HEAD --stat 2>/dev/null || echo "No git changes detected"

Instructions

Explain the target the user named in $ARGUMENTS (a file path, a function/symbol name, or "diff"/"changes" to explain recent edits). If no target was given, ask what they'd like explained.

Approach

  1. Read before explaining. Open the relevant file(s). For a symbol, use Grep to find its definition and key call sites. For "diff", run git diff HEAD and explain those changes.
  2. Lead with a one-sentence summary of what the code does and why it exists.
  3. Then give a structured walkthrough:
    • Inputs and outputs (parameters, return values, side effects)
    • The main control flow, step by step
    • Key data structures or algorithms involved
    • External dependencies it touches (DB, network, files, other modules)
  4. Call out anything non-obvious or surprising — implicit assumptions, edge-case handling, performance characteristics, or footguns.
  5. If the code looks buggy or fragile, note it briefly at the end, but don't turn this into a full review.

Rules

  1. Match the explanation depth to the audience — assume a competent engineer new to this codebase, not new to programming.
  2. Reference real symbols and file:line locations; don't speak in generalities.
  3. Use short paragraphs and bullet points. Include a tiny annotated snippet only when it clarifies a tricky part.
  4. Do not modify any files — this skill is read-only.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.