surveylisted

# 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. ``` Is the codebase surveyed? → Uses survey_stats → Returns: counts by analyzer (topology, entrypoints, churn) and kind ``` ### 2. Survey Run (`mcp__plugin_aide_aide__survey_run`) Run analyzers to populate survey data. Three analyzers available: - **topology** — Modules, packages, workspaces, build systems, tech stack detection - **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) ``` Survey this codebase → Uses survey_run (no analyzer param = run all) → Returns: entry counts per analyzer ``` ### 3. Survey List (`mcp__plugin_aide_aide__survey_list`) Browse entries filtered by analyzer, kind, or file path. No search query needed. **Kinds:** module, entrypoint, dependency, tech_stack, churn, submodule, workspace, arch_pattern ``` What modules are in this codebase? → Uses survey_list with kind=module → Returns: all module entries What technolo