loctreelisted

# Loctree — imaging before surgery Loctree supplies structural sight: repository shape, indexed literal occurrences, dependency neighborhoods, definition sites, runtime bridges, and blast radius. AICX supplies historical intent. Neither replaces direct source, manifests, tests, or a real runtime probe. ## Canonical Structural Gate For repo-specific work, this skill is the structural half of the `vc-init` procedure. `Loctree:loctree` must produce or refresh the Code-Derived Application Map before implementation, review, release, pruning, or deletion. If fresh `vc-init` evidence is absent, perform the init pass first and treat workflow-specific repo work as blocked until repo truth exists. If a task is not repo-specific, say so instead of pretending a map exists. ## Route by question | Need | Preferred surface | | --------------------------------------- | --------------------------------------- | | Broad task orientation | `loct context --task "..."` | | Quick repository overview | `loct repo-view` | | Directory wiring | `loct focus path/` | | File dependencies and consumers | `loct slice path/file` | | Rename/delete blast radius | `loct impact path/file` | | Exact identifier occurrences | `loct find Identifier` | | Definition