Explain codebase
Skill NSBen/skillfoundry/src/skillfoundry/data/starter_skills/explain-codebase
🔥 SkillFoundry (forge) — open, vendor-neutral toolchain for authoring, validating, testing & publishing AI agent skills. Works across Claude Code / Cursor / Codex / OpenCode / Cline. Ships 15 starter skills.
npx -y skills add NSBen/skillfoundry --skill explain-codebaseAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- 13 days oldThe repository was created 13 days ago. New is not bad, but a brand new repository carrying a familiar-sounding name is the shape a typosquat arrives in, and there has been no time for anyone else to find a problem with it.
- 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Use when you need to understand an unfamiliar repository or module and produce a structured walkthrough of how it works and where to change it.
The file declares its own license as MIT. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.
SKILL.md
1.2 KB, as published. Nobody here has run it
Explain Codebase
When to use
Invoke this skill when onboarding to a codebase, investigating a subsystem, or locating where a change should be made.
Steps
- Map the entry points and the high-level modules from the directory layout.
- Trace one concrete flow end to end (request, build, job) to anchor understanding.
- Note the key abstractions, data structures, and external dependencies.
- Identify the files most relevant to the user's question.
- Produce a layered summary: what it does, how it works, where to start.
Examples
- "Explain how authentication works in this repo"
- "Walk me through the request lifecycle"
References
Prefer file:line references and small diagrams over prose; stop before guessing behaviour you have not verified.