You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: AGENTS.md
+44Lines changed: 44 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -108,3 +108,47 @@ To conserve context space, load these resources as needed:
108
108
-[Jinja engine](common/jinja/README.md)
109
109
-[How to add a new model](docs/development/HOWTO-add-model.md)
110
110
-[PR template](.github/pull_request_template.md)
111
+
112
+
<!-- gitnexus:start -->
113
+
# GitNexus — Code Intelligence
114
+
115
+
This project is indexed by GitNexus as **llama.cpp** (60918 symbols, 114820 relationships, 300 execution flows). Use the GitNexus MCP tools to understand code, assess impact, and navigate safely.
116
+
117
+
> If any GitNexus tool warns the index is stale, run `npx gitnexus analyze` in terminal first.
118
+
119
+
## Always Do
120
+
121
+
-**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.
122
+
-**MUST run `gitnexus_detect_changes()` before committing** to verify your changes only affect expected symbols and execution flows.
123
+
-**MUST warn the user** if impact analysis returns HIGH or CRITICAL risk before proceeding with edits.
124
+
- When exploring unfamiliar code, use `gitnexus_query({query: "concept"})` to find execution flows instead of grepping. It returns process-grouped results ranked by relevance.
125
+
- When you need full context on a specific symbol — callers, callees, which execution flows it participates in — use `gitnexus_context({name: "symbolName"})`.
126
+
127
+
## Never Do
128
+
129
+
- NEVER edit a function, class, or method without first running `gitnexus_impact` on it.
130
+
- NEVER ignore HIGH or CRITICAL risk warnings from impact analysis.
131
+
- NEVER rename symbols with find-and-replace — use `gitnexus_rename` which understands the call graph.
132
+
- NEVER commit changes without running `gitnexus_detect_changes()` to check affected scope.
133
+
134
+
## Resources
135
+
136
+
| Resource | Use for |
137
+
|----------|---------|
138
+
|`gitnexus://repo/llama.cpp/context`| Codebase overview, check index freshness |
139
+
|`gitnexus://repo/llama.cpp/clusters`| All functional areas |
140
+
|`gitnexus://repo/llama.cpp/processes`| All execution flows |
IMPORTANT: Ensure you’ve thoroughly reviewed the [AGENTS.md](AGENTS.md) file before beginning any work.
2
+
3
+
<!-- gitnexus:start -->
4
+
# GitNexus — Code Intelligence
5
+
6
+
This project is indexed by GitNexus as **llama.cpp** (60918 symbols, 114820 relationships, 300 execution flows). Use the GitNexus MCP tools to understand code, assess impact, and navigate safely.
7
+
8
+
> If any GitNexus tool warns the index is stale, run `npx gitnexus analyze` in terminal first.
9
+
10
+
## Always Do
11
+
12
+
-**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.
13
+
-**MUST run `gitnexus_detect_changes()` before committing** to verify your changes only affect expected symbols and execution flows.
14
+
-**MUST warn the user** if impact analysis returns HIGH or CRITICAL risk before proceeding with edits.
15
+
- When exploring unfamiliar code, use `gitnexus_query({query: "concept"})` to find execution flows instead of grepping. It returns process-grouped results ranked by relevance.
16
+
- When you need full context on a specific symbol — callers, callees, which execution flows it participates in — use `gitnexus_context({name: "symbolName"})`.
17
+
18
+
## Never Do
19
+
20
+
- NEVER edit a function, class, or method without first running `gitnexus_impact` on it.
21
+
- NEVER ignore HIGH or CRITICAL risk warnings from impact analysis.
22
+
- NEVER rename symbols with find-and-replace — use `gitnexus_rename` which understands the call graph.
23
+
- NEVER commit changes without running `gitnexus_detect_changes()` to check affected scope.
24
+
25
+
## Resources
26
+
27
+
| Resource | Use for |
28
+
|----------|---------|
29
+
|`gitnexus://repo/llama.cpp/context`| Codebase overview, check index freshness |
30
+
|`gitnexus://repo/llama.cpp/clusters`| All functional areas |
31
+
|`gitnexus://repo/llama.cpp/processes`| All execution flows |
0 commit comments