survey

# Codebase Survey **Recommended model tier:** balanced (sonnet) - this skill performs structured queries Understand the structure, technology, entry points, and change hotspots of a codebase. Survey describes WHAT the codebase IS — not code problems (use `findings` for that). ## Available Tools ### 1. Survey Stats (`mcp__plugin_aide_aide__survey_stats`) **Start here.** Get an overview of what has been surveyed: total entries, breakdown by analyzer and kind, and per-analyzer freshness (the git commit each analyzer last ran at, and how many commits behind HEAD it is). ``` Is the codebase surveyed? → Uses survey_stats → Returns: counts by analyzer (topology, entrypoints, churn, modules) and kind, plus freshness vs git HEAD ``` If freshness shows an analyzer is commits behind HEAD, re-run survey_run before trusting its data. ### 2. Survey Run (`mcp__plugin_aide_aide__survey_run`) Run analyzers to populate survey data. Three analyzers available: - **topology** — Packages, workspaces, build systems, tech stack detection (filesystem view) - **entrypoints** — main() functions, HTTP handlers, gRPC services, CLI roots (cobra/urfave). Uses code index when available; falls back to file scanning - **churn** — Git history hotspots (files/dirs that change most often) - **modules** — Structural modules discovered by clustering the import/reference graph: what files actually belong together, which directory layout can hide. Requires the code index (`aide code index`) ``` Survey thi...