docs(AGENTS): auto-sync from SIN-Code-Bundle

Author: Delqhi

AGENTS.md

@@ -101,10 +101,6 @@ sin-code orchestrate --action add --title "Feature implementieren" --tags "urgen
 - **VOR jedem API-Call:** Immer `sin-harvest` mit Caching und Struktur-Extraktion nutzen
 - **Für jede Planung:** Immer `sin-orchestrate` mit Dependencies und Rollback-Plan nutzen
 
-### MCP Server State
-
-Both `sin-code-bundle` (Python CLI, legacy) and `sin-code` (Go unified binary, v1.0.0+) are currently registered in `opencode.json`. The Go unified binary (`sin-code`) is the modern recommended approach and supersedes the standalone Python binaries. Agents should prefer `sin-code` subcommands over the legacy `~/.local/bin/<tool>` paths.
-
 ### Versionen (aktuell)
 
 | Tool | Version | Status |
@@ -486,3 +482,47 @@ sin sin-code agents-md --output AGENTS.md
 ## Version
 
 v0.2.0
+
+<!-- gitnexus:start -->
+# GitNexus — Code Intelligence
+
+This project is indexed by GitNexus as **SIN-Code-Bundle** (8727 symbols, 15372 relationships, 252 execution flows). Use the GitNexus MCP tools to understand code, assess impact, and navigate safely.
+
+> If any GitNexus tool warns the index is stale, run `npx gitnexus analyze` in terminal first.
+
+## Always Do
+
+- **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.
+- **MUST run `gitnexus_detect_changes()` before committing** to verify your changes only affect expected symbols and execution flows.
+- **MUST warn the user** if impact analysis returns HIGH or CRITICAL risk before proceeding with edits.
+- When exploring unfamiliar code, use `gitnexus_query({query: "concept"})` to find execution flows instead of grepping. It returns process-grouped results ranked by relevance.
+- When you need full context on a specific symbol — callers, callees, which execution flows it participates in — use `gitnexus_context({name: "symbolName"})`.
+
+## Never Do
+
+- NEVER edit a function, class, or method without first running `gitnexus_impact` on it.
+- NEVER ignore HIGH or CRITICAL risk warnings from impact analysis.
+- NEVER rename symbols with find-and-replace — use `gitnexus_rename` which understands the call graph.
+- NEVER commit changes without running `gitnexus_detect_changes()` to check affected scope.
+
+## Resources
+
+| Resource | Use for |
+|----------|---------|
+| `gitnexus://repo/SIN-Code-Bundle/context` | Codebase overview, check index freshness |
+| `gitnexus://repo/SIN-Code-Bundle/clusters` | All functional areas |
+| `gitnexus://repo/SIN-Code-Bundle/processes` | All execution flows |
+| `gitnexus://repo/SIN-Code-Bundle/process/{name}` | Step-by-step execution trace |
+
+## CLI
+
+| Task | Read this skill file |
+|------|---------------------|
+| Understand architecture / "How does X work?" | `.claude/skills/gitnexus/gitnexus-exploring/SKILL.md` |
+| Blast radius / "What breaks if I change X?" | `.claude/skills/gitnexus/gitnexus-impact-analysis/SKILL.md` |
+| Trace bugs / "Why is X failing?" | `.claude/skills/gitnexus/gitnexus-debugging/SKILL.md` |
+| Rename / extract / split / refactor | `.claude/skills/gitnexus/gitnexus-refactoring/SKILL.md` |
+| Tools, resources, schema reference | `.claude/skills/gitnexus/gitnexus-guide/SKILL.md` |
+| Index, status, clean, wiki CLI commands | `.claude/skills/gitnexus/gitnexus-cli/SKILL.md` |
+
+<!-- gitnexus:end -->