Loctree/loctree
Skill Claude CodeCodex
Part of loctree
Pursue structural signals — dead code, cycles, duplicate exports (twins), hotspots, runtime traces, command/event/pipeline graphs. Use during cleanup, audit, refactor planning, or when investigating "is this used?" questions at module/system scope. Triggers on phrases "follow signals", "find dead code", "find cycles"…
Loctree/loctree
Skill Claude CodeCodex
Part of loctree
Score conceptual smear (drift, spread, runtime centrality, authority diversity, drift risk, closure evidence) across two or more task framings on the canonical 0..15 rubric. Use BEFORE running vc-polarize, BEFORE choosing a doctrine cut, or whenever an agent needs structural evidence for the abort/memo/pass/doctrine…
Loctree/loctree
Skill Claude CodeCodex
Part of loctree
Structural and literal repository perception before edits, deletes, refactors, or unfamiliar-code work. Use context/repo-view/focus/slice/impact/find/follow to establish scope, dependencies, blast radius, exact occurrences, and analyzer coverage before acting.
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: