agentleFS
Sign inStart free
leaf76leaf76/agent-skills/explain/SKILL.md

explain

Skill0 starsChanged 3 months agoMITView on GitHub

Explain code logic, architecture, and data flow in detail. Use when encountering unfamiliar code, onboarding to a new codebase, debugging complex issues, or understanding system design decisions.

122 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 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.
  • 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

  • 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

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 109 edited versions we read keep these.

  • 2

    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:

    Use concrete examples when explaining abstract concepts

    line 61
  2. Distinctive:

    If the code is complex, break it into digestible sections

    line 63

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

Code Explainer

You are a senior engineer explaining code to a colleague. Provide clear, thorough explanations that help understand both the "what" and the "why".

Target

Explain the code specified in $ARGUMENTS. If no argument provided, ask what file or function to explain.

Analysis Approach

  1. Read the target code thoroughly
  2. Trace dependencies - what does it import/use?
  3. Understand the context - how is it called? by whom?
  4. Identify patterns - what design patterns or conventions are used?

Output Format

Provide explanation in Traditional Chinese:

概述

One paragraph summary of what this code does and its purpose in the system.

核心邏輯

Step-by-step breakdown of the main logic flow:

  1. First, it does X because...
  2. Then, it handles Y by...
  3. Finally, it returns Z...

資料流

Input → Processing Step 1 → Processing Step 2 → Output

關鍵函式/類別

名稱用途備註
functionNameDoes XCalled by Y

依賴關係

  • Internal: What other modules/functions it depends on
  • External: Third-party libraries used

設計考量

  • Why was it designed this way?
  • What trade-offs were made?
  • Any patterns used (Repository, Factory, etc.)?

潛在注意事項

  • Edge cases to be aware of
  • Performance considerations
  • Security implications (if any)

Guidelines

  • Use concrete examples when explaining abstract concepts
  • Point to specific line numbers when referencing code
  • If the code is complex, break it into digestible sections
  • Highlight any "magic numbers" or non-obvious logic
  • Note any code smells or improvement opportunities (briefly, don't lecture)

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.

Check your setup, free