explore-codebase
Explore Codebase
Use the code-review graph to understand the repository before editing.
Core Rules
- Always start with
get_minimal_context_tool(task="<your task>"). - Use
detail_level="minimal"unless more detail is needed. - Prefer graph results for architecture, communities, flows, hubs, bridges, and impact paths.
- If graph tools are unavailable or empty, continue with
rg, manifests, README files, and config inspection.
Workflow
- Get compact context with
get_minimal_context_tool. - Build or update the graph if it is empty or stale.
- Use
get_architecture_overview_tool()for major boundaries. - Use
list_communities_tool(detail_level="minimal")to identify modules. - Use
list_flows_tool(detail_level="minimal")for execution paths. - Use
get_hub_nodes_tool()andget_bridge_nodes_tool()for risky chokepoints.
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.
7build-graph
Build or update the code review knowledge graph. Use before safe-code audits, refactors, reviews, debugging, or when the graph may be stale.
1review-changes
Review working-tree, branch, or PR changes using graph change detection, blast-radius analysis, affected flows, and test coverage checks.
1debug-issue
Systematically debug issues using graph-powered code navigation, recent-change detection, affected flows, and targeted verification.
1