agentsclimarketplace

Codebase navigator

Skill ahmadulhoq/agentskel/.agents/skills/codebase-navigator

When searching for code, tracing a bug, or understanding how modules connect. Use before grepping blindly — consult the index first.From its SKILL.md

Install
npx -y skills add ahmadulhoq/agentskel --skill codebase-navigator

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

  • 13 stars13 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 file declares

Copied from the file, not written here

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

2.0 KB, as published. Nobody here has run it

Codebase Navigator

Purpose: Use the project's indexed knowledge (MAP.md, SYMBOLS.md) to find code efficiently. The cartographer has already mapped the codebase — use the map.


What the index contains

FileWhat it tells youWhen to use it
MAP.mdModule registry — every module, its responsibility, key entry points, critical flowsWhich module owns this? How do modules connect? What's the end-to-end flow?
SYMBOLS.mdSymbol index — every class and named function with file pathsWhere is this class/function defined? What functions does this class have?
symbols/*.mdPer-module symbol files (split mode only)Full symbol table for a specific module

How to use them

Finding where something lives

  1. Check SYMBOLS.md — if it's an index (split mode), find the module row
  2. Read symbols/[module].md for the full symbol table of that module
  3. If symbols/ doesn't exist (single-file mode), SYMBOLS.md has everything directly

Understanding module ownership

  1. Check MAP.md for the module that owns the responsibility
  2. Read the module's key entry points to orient yourself

Tracing a flow

  1. Check MAP.md Critical Business Logic Flows for documented flows
  2. Follow the entry points listed there

Finding callers and implementation details

Grep is the right tool for this — the index tells you where things are defined, not who calls them. Once you've located the file via SYMBOLS.md, grep for callers.

When to skip the index

  • You already have the exact file path (e.g. from a TECH_DEBT entry or error stack trace)
  • You're searching for a string literal, log message, or error code (not a symbol)
  • The index is stale (check the timestamp at the top of each file)

No gate. This is an advisory skill, not a mandatory procedure.

Keep looking

Skills are one crate of 611,178. 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.