agentleFS
Sign inStart free
VinkyDevVinkyDev/vibestart/.agents/skills/explain/SKILL.md

explain

Skill289 starsChanged 29 days agoMITView on GitHub

Explain how a slice of this repository works, from the current code. Use before changing a module you have not read, or when asked how something works, why it is built this way, or where a behavior lives.

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

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

  • 0

    Common

    Most of the 109 edited versions we read keep these.

  • 0

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Report drift: When the code contradicts docs/architecture.md, AGENTS.md, or GLOSSARY.md, say so and name the line.

    line 11

“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

An explainer is read once, so it trades completeness for the path a reader follows. Ground every claim in the code as it is now.

  1. Frame. Turn the request into one question and name the entry point: a CLI command (apps/cli/src/cli.ts), a generator call (generate in packages/core/src/generator.ts), a vp run stacks subcommand (packages/integrations/src/stacks.ts), a Studio route (apps/web/src/routes/), or a CI job (.github/workflows/ci.yml). AGENTS.md (Map) and docs/architecture.md say which package owns what. Done when you can say the question in one sentence and point at the file where the path starts.
  2. Trace. Follow the path from the entry point to its effect: reading files, calling functions, and checking the test that owns each step. Note each place it branches on a choice (ctx.has, a kind, a package manager, a platform). Done when every step of the path has a file:line.
  3. Explain. Lead with a call tree or data-flow sketch of that path, then a short paragraph per step: what it owns, the invariant it keeps, and the decision docs/architecture.md records for it. Use the terms in GLOSSARY.md. End with the test to read or run to see it work, and what a change here reaches (stacks, goldens, the Studio, the CLI skill). When the reader asks for a visual, render the sketch as a diagram.
  4. Report drift. When the code contradicts docs/architecture.md, AGENTS.md, or GLOSSARY.md, say so and name the line. A stale document is a bug.

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