Navegador's `ci` subcommand is designed for non-interactive use in pipelines. All CI commands emit structured output and use exit codes that CI systems understand.
4
5
---
6
7
## CI commands
8
9
### `navegador ci ingest`
10
11
Ingest the repo and output a machine-readable summary. Exits non-zero on errors.
12
13
```bash
14
navegador ci ingest ./src
15
```
16
17
JSON output (always on in CI mode):
18
19
```json
20
{
21
"status": "ok",
22
"nodes_created": 1240,
23
"nodes_updated": 38,
24
"edges_created": 4821,
25
"files_processed": 87,
26
"errors": [],
27
"duration_seconds": 4.2
28
}
29
```
30
31
### `navegador ci stats`
32
33
Print graph statistics as JSON. Use to track graph growth over time or assert a minimum coverage threshold.
34
35
```bash
36
navegador ci stats
37
```
38
39
```json
40
{
41
"repositories": 1,
42
"files": 87,
43
"classes": 143,
44
"functions": 891,
45
"methods": 412,
46
"concepts": 14,
47
"rules": 9,
48
"decisions": 6,
49
"total_edges": 4821
50
}
51
```
52
53
### `navegador ci check`
54
55
Run assertion checks against the graph. Exits non-zero if any check fails.
56
57
```bash
58
navegador ci check
59
```
60
61
Checks run by default:
62
63
| Check | Condition for failure |
64
|---|---|
65
| `no-cycles` | Circular import chains detected |
66
| `min-coverage` | Functions with no tests below threshold |
67
| `critical-rules` | Code violates a `critical`-severity rule |
68
| `dead-code` | High-confidence dead code above threshold |
69
70
Configure checks in `navegador.toml`:
71
72
```toml
73
[ci.checks]
74
no-cycles = true
75
min-coverage = 60 # percent of functions with tests
76
critical-rules = true
77
dead-code = false # disable dead-code check
78
79
[ci.thresholds]
80
dead_code_max = 10 # fail if more than 10 dead-code candidates
81
uncovered_max_percent = 40 # fail if more than 40% of functions lack tests
82
```
83
84
### Running specific checks
85
86
```bash
87
navegador ci check --only no-cycles
88
navegador ci check --only critical-rules,min-coverage
89
navegador ci check --skip dead-code
90
```
91
92
---
93
94
## Exit codes
95
96
| Code | Meaning |
97
|---|---|
98
| `0` | Success — all checks passed |
99
| `1` | Check failure — one or more assertions failed |
100
| `2` | Ingest error — files could not be parsed (partial result) |
101
| `3` | Configuration error — bad flags or missing config |
const body = `## Navegador impact analysis\n\n${impact.summary}`
188
github.rest.issues.createComment({
189
issue_number: context.issue.number,
190
owner: context.repo.owner,
191
repo: context.repo.repo,
192
body
193
})
194
```
195
196
---
197
198
## Editor integration
199
200
### VS Code
201
202
Install the [Navegador VS Code extension](https://marketplace.visualstudio.com/items?itemName=ConflictHQ.navegador) for inline context overlays and on-save re-ingest.
203
204
Or configure a task in `.vscode/tasks.json` to run on save:
205
206
```json
207
{
208
"version": "2.0.0",
209
"tasks": [
210
{
211
"label": "Navegador: re-ingest on save",
212
"type": "shell",
213
"command": "navegador ingest ${file}",
214
"group": "build",
215
"presentation": {
216
"reveal": "silent",
217
"panel": "shared"
218
},
219
"runOptions": {
220
"runOn": "folderOpen"
221
}
222
}
223
]
224
}
225
```
226
227
### Neovim
228
229
Add a post-write autocmd to trigger incremental ingest:
Set these as [GitHub Actions secrets](https://docs.github.com/en/actions/security-guides/using-secrets-in-github-actions) and reference them in your workflow with `${{ secrets.NAME }}`.