agentsclimarketplace
Sign in

Explain codebase

Skill KhaledSaeed18/dotclaude/skills/engineering/explain-codebase

Onboard to an unfamiliar codebase by mapping its architecture, entry points, and data flow. Use when starting work in a new or unknown repository and you need a navigable mental model fast.From its SKILL.md

Install
npx -y skills add KhaledSaeed18/dotclaude --skill explain-codebase

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 4 stars4 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.

SKILL.md

2.4 KB, 472 tokens by cl100k_base, as published. Nobody here has run it

Build a navigable map of this repository so the reader can find their way around and start contributing. Work from evidence in the repo, not assumptions about the stack.

Orient first

  • Identify the project type and stack from manifests and config (e.g. package.json, pyproject.toml, go.mod, Cargo.toml, pom.xml, Gemfile, Dockerfiles, CI config). Note the build, test, and run commands.
  • Read the README, docs, and any CONTRIBUTING or architecture notes before reading code, but verify their claims against the tree rather than trusting them blindly.
  • Get the shape of the tree: the top-level directories and what each is responsible for.

Map the architecture

  • Find the entry points: CLI mains, server bootstraps, route registrations, scheduled jobs, queue consumers, lambda/handler exports, UI roots. List them with file:line.
  • Identify the layers / modules and how they depend on each other (e.g. interface → service/domain → data access → external integrations). Note the boundaries that matter.
  • Locate cross-cutting concerns: config/env loading, auth, logging, error handling, database/connection setup, feature flags.

Trace the data flow

  • Pick one or two representative operations (or whatever the user asked to focus on) and follow them end to end: input → validation → core logic → persistence/external calls → response.
  • Show each path as a short sequence of file:line hops the reader can click through.
  • Call out where state lives (databases, caches, queues, external services) and how it's accessed.

Report

Produce, concisely:

  1. Summary: one paragraph on what this project is and does.
  2. Architecture map: the layers/modules and their responsibilities.
  3. Entry points: where execution starts, with paths.
  4. Key flows: the traced paths.
  5. Conventions & gotchas: naming, patterns, where to add a new feature, anything surprising.
  6. Where to look next: the 3 to 5 files most worth reading first.

Prefer precise file:line references over prose. Flag anything you were unsure about rather than guessing.

What ships with it: 1 file

819 B alongside SKILL.md

Gives 0 of the 12 instructions most codebase onboarding skills give in 472 tokens

Counted across 307 of the 325 authors here whose files we hold, read 2026-09-06

  • Focus first session on one successful outcomein 34 of 307, across 15 files
  • Show progress and celebrate completionsin 32 of 307, across 13 files
  • Prefer interactive doing over tutorialsin 32 of 307, across 13 files
  • Remove every step between signup and core valuein 32 of 307, across 13 files
  • Keep checklists to 3-7 items ordered by valuein 32 of 307, across 13 files
  • Read product marketing context before asking questionsin 28 of 307, across 13 files
  • Focus fixes on the biggest funnel drop-offsin 22 of 307, across 7 files
  • Define activation as the action most correlated with retentionin 20 of 307, across 6 files
  • Give one clear next action at every stepin 19 of 307, across 8 files
  • Understand product context and current state before recommendingin 15 of 307, across 3 files
  • Limit guided tours to five dismissable stepsin 15 of 307, across 6 files
  • Trace one request from entry to responsein 14 of 307, across 8 files

Said here and by no other author read

  • Identify project type and stack from manifests
  • Note the build, test, and run commands
  • Get the shape of the top-level directories
  • Find entry points with file:line references
  • Map layers and their dependencies
  • Locate cross-cutting concerns

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.

Keep looking

Skills are one crate of 325,949. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.