Orient. Read README/AGENTS.md, the project config (pyproject/package.json/ Cargo.toml), and the directory layout. Learn how it's built, tested, and run.
Find the entrypoints. Locate where execution starts and the main modules. Glob for structure, Grep for symbols.
Trace to the target. For a change, find the exact code that owns the behaviour — search by symbol/string, read the function AND its callers. Confirm you've found the real source, not a generated/duplicated copy.
Learn the conventions. Note the existing patterns (naming, error handling, test layout, comment density) so your change reads like the surrounding code.
For broad exploration, delegate. If mapping spans many files, dispatch a subagent (see delegating-to-subagents) to sweep and report, keeping your context focused.
Only then edit — and read a file fully before you Edit it.

Más de este repositorio

mismo repositorio

Catch bad React in your changes — run react-doctor's deterministic scan and fix what it flags

Run a verifiable security scan (vulns, secrets, misconfig) over code you wrote or deps you added, before calling the work done

Drive a real browser verifiably — navigate, snapshot, act BY INDEX, extract; every step provable

Run multi-agent work as ONE provable causal DAG — parallel subagents, an Orchestrate graph, an immutable spec-seed

Author or connect a Model Context Protocol server so an agent gains new tools

Build automated pipelines that gate merges and ship reliably

name	exploring-a-codebase
description	Map an unfamiliar codebase and find the right place to change before editing
version	1
trust	built-in

Don't edit code you haven't located in context. A few minutes mapping prevents editing the wrong file or breaking a caller you didn't know about.

Orient. Read README/AGENTS.md, the project config (pyproject/package.json/ Cargo.toml), and the directory layout. Learn how it's built, tested, and run.
Find the entrypoints. Locate where execution starts and the main modules. Glob for structure, Grep for symbols.
Trace to the target. For a change, find the exact code that owns the behaviour — search by symbol/string, read the function AND its callers. Confirm you've found the real source, not a generated/duplicated copy.
Learn the conventions. Note the existing patterns (naming, error handling, test layout, comment density) so your change reads like the surrounding code.
For broad exploration, delegate. If mapping spans many files, dispatch a subagent (see delegating-to-subagents) to sweep and report, keeping your context focused.
Only then edit — and read a file fully before you Edit it.