agentsclimarketplace
Sign in

Explore codebase

Skill vaibhavsaxena022/skills/explore-codebase

Understand the relevant part of a codebase BEFORE changing it. Use at the start of any bug fix or feature in an unfamiliar area. Maps the entry points, data flow, and conventions, and pinpoints where the change belongs — without modifying anything.From its SKILL.md

Install
npx -y skills add vaibhavsaxena022/skills --skill explore-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

  • 0 stars0 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

1.3 KB, 167 tokens by cl100k_base, as published. Nobody here has run it

Explore Codebase

Build an accurate mental model before making changes.

Steps

  1. Locate the entry points for the feature/bug — routes, handlers, jobs, CLI commands.
  2. Trace the flow: request → service → data layer → external calls. Note the key types and boundaries.
  3. Identify the conventions to follow: error handling, logging, testing, dependency injection, naming.
  4. Find the smallest place the change belongs; note everything it will affect.
  5. Summarize: the flow, the files that matter, the conventions, and the proposed change location.

Rules

  • Read-only — do not modify code in this pass.
  • Cite findings as path:line so they're checkable.
  • Look for an existing pattern to reuse before proposing anything new.

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.

Keep looking

Skills are one crate of 326,614. 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.