orchex006/axiom
Code graph context, change impact and Axiom operations for coding assistants
Install, repair, check, update or remove Axiom through the released axm CLI and verified platform-specific bootstrap scripts. Check prerequisites and target support, keep approvals scoped to the printed plan, and report unverified outcomes honestly.
Create the first Axiom code graph for a selected solution using the installed graph engine, then verify published generations, source coverage and a bounded query. Use for initial indexing or an explicitly requested full rebuild, not routine edits.
Publish an explicit Git-tracked graph checkpoint from a named source selector, so a checkpoint is never committed against source that is not in the commit.
Answer code questions and build bounded context through Axiom MCP graph tools before reading relevant source. Use for symbols, callers, dependencies and code relationships; graph construction and file watching belong to graph-build and graph-watch.
Diagnose graph service problems by separating a missing daemon, a partial snapshot and a bounded timeout into distinct recovery steps without deleting or rebuilding live state.
Review a change through Axiom MCP graph queries, compare expected dependencies with observed impact and report unresolved limits instead of assuming no impact.
Install and verify the Axiom ecosystem in the contract order by reading the installation contract, probing every declared prerequisite, stopping on an unsatisfied or unknown prerequisite, and reporting unbuilt or unverified steps as unbuilt or unverified.
Reconcile only the dirty scope of the repository graph at coherent change boundaries, then verify and report freshness and coverage without rebuilding the whole graph.
Check and plan an axiom component or skills-bundle update, obtain scoped human approval for the exact plan digest, and apply only that approved plan.
Keep an existing Axiom code graph updated as source files change by running the graph engine's watcher/reconcile loop, and verify automatic publication after a save. Use for continuous graph refresh, not hot reloading application binaries or models.