review-changes
Review Changes
Perform a focused code review of changed code and its blast radius.
Core Rules
- Use code-review stance: findings first, ordered by severity, with file and line references where possible.
- Start with
get_minimal_context_tool(task="review changes"). - Run
build_or_update_graph_tool()before review if the graph is stale. - Prefer
detect_changes_tool(detail_level="minimal")for risk-scored deltas. - Read full source only for changed or high-impact files.
- If graph tools are unavailable, review with
git diff,rg, and direct file reads.
Scope Modes
- No argument: review current working tree against default diff base.
- File or function argument: review that target and its graph impact.
- Branch argument: review branch diff against
mainormaster. - PR number: inspect the checked-out PR branch or use local git diff if available.
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.
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