CodeNib AGENTS.md

AGENTS.md

CodeNib is a Python 3.10+ code analysis agent with tree-sitter chunking, semantic graph construction, hybrid retrieval, and MCP-facing search tools. Use this file as the repo-level contract for Codex and other code agents.

Layered Objectives

Work in this order unless the user gives a narrower task:

1. Protect main: do not merge draft PRs, PRs with unresolved code failures, or stacked PRs whose dependency chain is not clear.
2. Make changes reviewable: keep commits focused, preserve existing ownership boundaries, and avoid unrelated refactors.
3. Verify the changed surface: run the smallest relevant test first, then widen to the job or marker tier that matches the risk.
4. Keep stacked work coherent: merge or rebase dependencies before dependents, and re-check diffs after a base branch changes.
5. Codify repeated feedback here or in the nearest directory-specific rules file so future agents do not repeat the same mistake.

For broad multi-step work, keep an explicit layered goal active until the requested surface is implemented, locally verified, documented, and reconciled with relevant PRs/issues. Do not mark a broad goal complete just because a single subgoal landed. Prefer local targeted verification and continued implementation over waiting on slow remote CI; run the remote/slow tier after the merge queue or feature batch is otherwise coherent.

For the current multi-language SCIP cold-start and acceleration program, use docs/scip_multilanguage_roadmap.md as the durable objective record. Update it whenever a backend is promoted, a C++ acceleration gate changes, or a related issue/PR is closed.

For storage scope and subtraction, use docs/storage_backend_roadmap.md as the durable objective record. Update it whenever the Wiki database boundary changes, a retained compatibility surface is removed, or a proposal attempts to reopen the generic backend program.

For the cognitive-debt reduction program, use docs/cognitive_debt_roadmap.md as the durable objective record. Update it whenever a package changes lifecycle class, an experimental surface is retired, an architectural dependency direction changes, or a subtraction iteration is completed.