bearing-guidelisted

# GitNexus Guide Quick reference for all GitNexus MCP tools, resources, and the knowledge graph schema. ## Always Start Here For any task involving code understanding, debugging, impact analysis, or refactoring: 1. **Read `gitnexus://repo/{name}/context`** — codebase overview + check index freshness 2. **Match your task to a skill below** and **read that skill file** 3. **Follow the skill's workflow and checklist** > If step 1 warns the index is stale, run `npm run bearing:agent-refresh` (autonomous, hook-pre-approved) — never ask the user to analyze. ## Skills | Task | Skill to read | | -------------------------------------------- | ------------------- | | Understand architecture / "How does X work?" | `bearing-exploring` | | Blast radius / "What breaks if I change X?" | `bearing-impact-analysis` | | Trace bugs / "Why is X failing?" | `bearing-debugging` | | Rename / extract / split / refactor | `bearing-refactoring` | | Add a feature / new code (reuse + wire in) | `bearing-feature-dev` | | What to test / coverage gaps | `bearing-testing` | | Slow / hot path / cost optimization | `bearing-performance` | | Judge structure (coupling, cycles, god objs) | `bearing-architecture-review` | | Work across layers (controller→repo→model) | `bearing-layered-systems` | | Milestone deep audit (opinionated, verified) | `bearing-microscope`