ecp

What problem does it solve? Understanding code structure by grepping text is slow and error-prone: you cannot tell who calls a function, what breaks if it changes, or which routes and contracts exist. This Skill answers structural questions against a pre-built code graph in sub-30ms queries, replacing manual file fan-out with deterministic graph lookups. ## Core Features & Use Cases - Symbol lookup and inspection: ecp find locates definitions (exact, fuzzy, or BM25-ranked), and ecp inspect returns a symbol's signature, body, edges, and callers in one shot. - Impact and blast radius: ecp impact lists upstream callers before a refactor or rename, supports git-baseline diff mode, and classifies path-literal read/write sites to catch filename split-brain bugs. - Architecture queries: ecp routes, ecp contracts, ecp tool-map, and ecp processes surface HTTP routes, cross-repo API contracts, external egress calls, and ordered execution flows; ecp cypher handles arbitrary graph questions. - Use Case: Before renaming a shared utility function, run ecp impact <name> to see every caller with file:line, cross-check a suspiciously low count with grep, then apply ecp rename for an AST-aware multi-file rename. ## Quick Start Ask the assistant to use ecp to find who calls a specific function and what breaks if it changes before refactoring it.