build-graph
Build Graph
Build or incrementally update the persistent code knowledge graph for the current repository.
Core Rules
- Start with
get_minimal_context_tool(task="build graph")when available. - Use
build_or_update_graph_tool()for normal updates. - Use
build_or_update_graph_tool(full_rebuild=True)for first setup, branch switches, parser failures, or obviously stale graph state. - Verify with
list_graph_stats_tool()after building. - If graph tools are unavailable, do not block the parent workflow. Report the missing graph and continue with manual repo inspection.
Workflow
- Check graph status with
list_graph_stats_tool(). - If the graph has no files, nodes, edges, or last update, run a full build.
- Otherwise run an incremental update.
- Verify files, nodes, edges, languages, and update time.
- Report build status and any parse or language coverage gaps.
More from afu-it/safe-code
safe-code
Full repo hygiene in one pass. Uses /safe-code for first-time setup, /safe-code --continue for context-safe resume, and /safe-code --save for handoff + local commit. Detects the active agent, initializes all continuity docs inside the current project only, audits and removes dead code in safe slices, refactors in place, and keeps docs in sync. /safe-code --save creates or uses a local git repo and commits locally only — it never pushes to a remote. Universal git remote detection is informational only. Use when asked to do a full cleanup, full hygiene pass, /safe-code, or maintain a repo in one go.
9codebase-pruner
Scan an entire codebase to detect and safely remove dead code such as unused functions, orphaned modules, unreferenced exports, stale configs, dead routes, and leftover workflow artifacts. Use when asked to clean up dead code, remove unused code, prune stale files, find orphaned modules, audit codebase bloat, or delete code left behind after a workflow or architecture change.
7safe-refactor-code
Refactor code safely in small verified slices while keeping repo continuity docs in sync. Uses code-review graph tools for rename previews, impact radius, affected flows, and post-change review when available. Use when an agent is asked to refactor, restructure, clean up, remove or replace code, modernize modules, or do follow-up hygiene in a repo.
7review-changes
Review working-tree, branch, or PR changes using graph change detection, blast-radius analysis, affected flows, and test coverage checks.
1explore-codebase
Navigate and understand codebase structure using the code-review graph. Use for repo orientation, AGENTS.md authoring, architecture mapping, or finding relevant code.
1debug-issue
Systematically debug issues using graph-powered code navigation, recent-change detection, affected flows, and targeted verification.
1