catch-me-uplisted

# Catch Me Up Answer the recurring comprehension questions about a codebase without the user having to formulate them each session. Most sessions are comprehension, not generation; this skill freezes the questions that repeat. The deliverable automates the question, not the understanding. Every claim cites its source so the user can check it against their own mental model: `file:line` for current code, and a commit hash, PR link, or changelog entry for history findings, whose evidence often no longer exists at any current `file:line`. Inference is labeled apart from what you read (the **align-on-intent** principle skill). Invoking this skill is the user's request to spawn every subagent it prescribes (per-mode explorers). A host default that gates the Agent tool on a user request is satisfied. ## Modes Pick the mode or modes the ask names. A bare "catch me up" runs the orientation sweep: architecture, convention, testing, and history at survey depth. | Mode | Level | Answers | | --- | --- | --- | | Architecture | global | module map, dependency direction, entry points | | Convention | local | naming patterns, lint rules, repo-specific idioms | | Feature trace | local | how one feature flows across modules | | Syntax | detailed | unfamiliar constructs or API surfaces | | Testing | detailed | test structure, fixtures, assertion patterns, how to run them | | History | cross-cutting | recent changes, deprecations, migration context | Routing: a feature trace is the **how**