agentleFS
eugnmueller-87eugnmueller-87/claude-blueprint/.claude/skills/explain/SKILL.md

explain

Skill1 starsChanged 5 months agoMITView on GitHub

Fast orientation on unfamiliar code — find the entry points, trace the data flow, name the 3 files that actually matter, and explain it in plain language. Use when landing in a new repo or module and needing the mental model before touching anything. Trigger phrases "explain this", "how does X work", "walk me through this code".

130 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use root-cause, resolve-conflicts and 9 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.
  • 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

  • ralphkraussSkill

    resolve-conflicts

    Resolve git merge conflicts or re-apply changes from a stale branch onto current main. Use when user says "resolve conflicts", "merge conflicts", "rebase branch", "branch is behind", "re-apply changes", "port branch", or a branch is too far behind main to merge cleanly.

    Also in 4 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

1 rule. 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 118 edited versions we read keep these.

  • 1

    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:

    Trace the main data flow: Follow ONE representative path end to end: input → transform → the core work (the API call, the query, the agent …

    line 22

“Common” is measured: kept by at least 6 in 10 of the 118 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

explain

Trigger: "explain this" / "how does X work" / "walk me through this code"

Standing rules: ../_conventions.md.

Give Eugen the mental model fast, in plain voice — no corporate filler, no restating the obvious. Lead with the one-sentence "what this is". Never invent behavior you didn't read; if the code is ambiguous, say so.

Steps

  1. Find the entry points. Locate where execution starts: __main__, a CLI argparse/click command, a FastAPI/Flask app, a bot handler, a LangGraph/agent graph definition, or the public functions a caller imports.
  2. Trace the main data flow. Follow ONE representative path end to end: input → transform → the core work (the API call, the query, the agent step) → output. Read the actual code; note where state or side effects live.
  3. Name the 3 files that matter. The ones you'd have to understand to change anything real. Skip config, tests, and glue. Say what each one owns.
  4. Surface the non-obvious. Anything a newcomer would trip on: a hidden coupling, an implicit contract, a "why is it done this way" decision, a place that reads env vars, a spot where errors are swallowed.
  5. Report (terse):
    • What it is: one sentence.
    • Flow: input → … → output, in 3–5 arrows.
    • The 3 files: path — what it owns.
    • Watch out for: the non-obvious bits. End with: "To change <the thing you'd likely want>, start in <file>."

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.