[docs] remove gitnexus stuff from agents.md

-79

1 changed file

expand all

AGENTS.md

-79

AGENTS.md

··· 139 139 - `[ingest] implement backfill buffer replay` 140 140 - `[api] add accurate count parameter to stats` 141 141 - `[db] migrate block storage to msgpack` 142 - 143 -  144 - # GitNexus — Code Intelligence 145 - 146 - This project is indexed by GitNexus as **hydrant** (1339 symbols, 3645 relationships, 113 execution flows). Use the GitNexus MCP tools to understand code, assess impact, and navigate safely. 147 - 148 - > If any GitNexus tool warns the index is stale, run `npx gitnexus analyze` in terminal first. 149 - 150 - ## Always Do 151 - 152 - - **MUST run impact analysis before editing any symbol.** Before modifying a function, class, or method, run `gitnexus_impact({target: "symbolName", direction: "upstream"})` and report the blast radius (direct callers, affected processes, risk level) to the user. 153 - - **MUST run `gitnexus_detect_changes()` before committing** to verify your changes only affect expected symbols and execution flows. 154 - - **MUST warn the user** if impact analysis returns HIGH or CRITICAL risk before proceeding with edits. 155 - - When exploring unfamiliar code, use `gitnexus_query({query: "concept"})` to find execution flows instead of grepping. It returns process-grouped results ranked by relevance. 156 - - When you need full context on a specific symbol — callers, callees, which execution flows it participates in — use `gitnexus_context({name: "symbolName"})`. 157 - 158 - ## When Debugging 159 - 160 - 1. `gitnexus_query({query: "<error or symptom>"})` — find execution flows related to the issue 161 - 2. `gitnexus_context({name: "<suspect function>"})` — see all callers, callees, and process participation 162 - 3. `READ gitnexus://repo/hydrant/process/{processName}` — trace the full execution flow step by step 163 - 4. For regressions: `gitnexus_detect_changes({scope: "compare", base_ref: "main"})` — see what your branch changed 164 - 165 - ## When Refactoring 166 - 167 - - **Renaming**: MUST use `gitnexus_rename({symbol_name: "old", new_name: "new", dry_run: true})` first. Review the preview — graph edits are safe, text_search edits need manual review. Then run with `dry_run: false`. 168 - - **Extracting/Splitting**: MUST run `gitnexus_context({name: "target"})` to see all incoming/outgoing refs, then `gitnexus_impact({target: "target", direction: "upstream"})` to find all external callers before moving code. 169 - - After any refactor: run `gitnexus_detect_changes({scope: "all"})` to verify only expected files changed. 170 - 171 - ## Never Do 172 - 173 - - NEVER edit a function, class, or method without first running `gitnexus_impact` on it. 174 - - NEVER ignore HIGH or CRITICAL risk warnings from impact analysis. 175 - - NEVER rename symbols with find-and-replace — use `gitnexus_rename` which understands the call graph. 176 - - NEVER commit changes without running `gitnexus_detect_changes()` to check affected scope. 177 - 178 - ## Tools Quick Reference 179 - 180 - | Tool | When to use | Command | 181 - |------|-------------|---------| 182 - | `query` | Find code by concept | `gitnexus_query({query: "auth validation"})` | 183 - | `context` | 360-degree view of one symbol | `gitnexus_context({name: "validateUser"})` | 184 - | `impact` | Blast radius before editing | `gitnexus_impact({target: "X", direction: "upstream"})` | 185 - | `detect_changes` | Pre-commit scope check | `gitnexus_detect_changes({scope: "staged"})` | 186 - | `rename` | Safe multi-file rename | `gitnexus_rename({symbol_name: "old", new_name: "new", dry_run: true})` | 187 - | `cypher` | Custom graph queries | `gitnexus_cypher({query: "MATCH ..."})` | 188 - 189 - ## Impact Risk Levels 190 - 191 - | Depth | Meaning | Action | 192 - |-------|---------|--------| 193 - | d=1 | WILL BREAK — direct callers/importers | MUST update these | 194 - | d=2 | LIKELY AFFECTED — indirect deps | Should test | 195 - | d=3 | MAY NEED TESTING — transitive | Test if critical path | 196 - 197 - ## Resources 198 - 199 - | Resource | Use for | 200 - |----------|---------| 201 - | `gitnexus://repo/hydrant/context` | Codebase overview, check index freshness | 202 - | `gitnexus://repo/hydrant/clusters` | All functional areas | 203 - | `gitnexus://repo/hydrant/processes` | All execution flows | 204 - | `gitnexus://repo/hydrant/process/{name}` | Step-by-step execution trace | 205 - 206 - ## Self-Check Before Finishing 207 - 208 - Before completing any code modification task, verify: 209 - 1. `gitnexus_impact` was run for all modified symbols 210 - 2. No HIGH/CRITICAL risk warnings were ignored 211 - 3. `gitnexus_detect_changes()` confirms changes match expected scope 212 - 4. All d=1 (WILL BREAK) dependents were updated 213 - 214 - ## CLI 215 - 216 - - Re-index: `npx gitnexus analyze` 217 - - Check freshness: `npx gitnexus status` 218 - - Generate docs: `npx gitnexus wiki` 219 - 220 -

Configure Feed

Configure Feed