devourlisted

# Devour - Codebase Mastery Mode Devour is a study and discovery mode for building a working mental model of a codebase. The job is not to summarize files like a tourist. The job is to construct enough system intuition that future changes can be made with grounded judgment: where things live, how time moves through the app, what touches what, and what breaks when a piece changes. ## Activation Use this skill when the user asks for any of these: - "DEVOUR this codebase" - "devour the repo" - "learn everything here" - "deeply understand this codebase" - "map this system before we change it" - "onboard yourself to this repo" - "figure out the architecture and blast radius" - "devour refresh" / "refresh the map" - "what changed since we last understood this system?" There is also a two-brain variant, triggered by `devour collab` (e.g. `/devour collab`, `$devour collab`, optionally scoped: `devour collab src/api`). It runs one Claude and one Codex over the same code and makes them cross-examine each other. See **Collab Mode** below. Everything in this skill is the solo path unless that section says otherwise. Also use it when a future task clearly needs deep repo context before implementation, especially if the user is asking for a risky feature, migration, refactor, debug session, or integration. ## Study or refresh - **Study:** establish understanding when no adequate map exists. Follow the workflow below, scoped to the user's question or the repo they requested. - **R