agentleFS
Sign inStart free
rpraharajrpraharaj/ai-sdlc/skills/explain-code/SKILL.md

explain-code

Skill0 starsChanged 15 days agoMITView on GitHub

Teach a feature or path from the code that exists — entry points, data flow, and what to change. Use when the user asks how X works, explain this, walk me through, or is onboarding onto a feature. Do not implement. Do not invent architecture the tree does not have.

48 other projects use a version of this, 1 of them edited.

Adopted by

Most recently taken up by

Used with

Projects with it also use copy-editing, pricing-strategy and 6 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.
  • silvainfmSkill

    copy-editing

    When the user wants to edit, review, or improve existing marketing copy. Also use when the user mentions 'edit this copy,' 'review my copy,' 'copy feedback,' 'proofread,' 'polish this,' 'make this better,' or 'copy sweep.' This skill provides a systematic approach to editing marketing copy through multiple focused passes.

    Also in 3 projects that use this

  • silvainfmSkill

    pricing-strategy

    When the user wants help with pricing decisions, packaging, or monetization strategy. Also use when the user mentions 'pricing,' 'pricing tiers,' 'freemium,' 'free trial,' 'packaging,' 'price increase,' 'value metric,' 'Van Westendorp,' 'willingness to pay,' or 'monetization.' This skill covers pricing research, tier structure, and packaging strategy.

    Also in 3 projects that use this

  • SentrySkill

    marketing-psychology

    When the user wants to apply psychological principles, mental models, or behavioral science to marketing. Also use when the user mentions 'psychology,' 'mental models,' 'cognitive bias,' 'persuasion,' 'behavioral science,' 'why people buy,' 'decision-making,' or 'consumer behavior.' This skill provides 70+ mental models organized for marketing application.

    Also in 3 projects that use this

  • GitHubSkill

    refactor

    Surgical code refactoring to improve maintainability without changing behavior. Covers extracting functions, renaming variables, breaking down god functions, improving type safety, eliminating code smells, and applying design patterns. Less drastic than repo-rebuilder; use for gradual improvements.

    Also in 4 projects that use this

  • OpenAISkill

    writing-plans

    Use when you have a spec or requirements for a multi-step task, before touching code

    Also in 4 projects that use this

  • GoogleSkill

    grill-me

    A relentless interview to sharpen a plan or design.

    Also in 7 projects that use this

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 41 edited versions we read keep these.

  • 3

    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:

    Read AGENTS.md. Skim the entry, the next 1–2 layers, data it reads/writes, and nearest tests.

    line 38
  2. Distinctive:

    Stop when you can say where it starts, what it does, and where an edit would go.

    line 39
  3. Distinctive:

    Write the tour from references/explain-template.md.

    line 40

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

Teach one path so the next edit is aimed. Do not implement. Do not map the whole repo (explore-codebase).

Is this the right skill?

SignalDo this instead
Whole repo map / commandsexplore-codebase
They want a changeshape-work after the tour
Invent a target systemstop — read the tree

Required inputs

  • A named symbol, file, route, or feature. If missing, pick the hottest match and say so, or ask one question and stop.
  • context/glossary.md if present (follow the pointer in AGENTS.md)

Human decisions (do not invent)

  • None. Do not invent types or services.

Procedure

  1. Read AGENTS.md. Skim the entry, the next 1–2 layers, data it reads/writes, and nearest tests.
  2. Stop when you can say where it starts, what it does, and where an edit would go.
  3. Write the tour from references/explain-template.md. Use names from this repo.

Output

  • Path: reply, or docs/explain/<slug>.md if they asked for a file
  • Template: references/explain-template.md

Quality bar

  • Starts at a real path or symbol
  • Call chain uses this repo’s names
  • No invented architecture
  • Tests named or none found

Done

The tour. Next: shape-work or implement-change if they want a change.

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.

Reviews can't be read right now.

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.

Check your setup, free