# Review Changes

> Perform a structured code review using change detection and impact

- Skill: `microsoft365dsc/review-changes` (Agent Skill, multi-file: 2 files)
- Install (CLI): `npx skillmds@latest add microsoft365dsc/review-changes`
- Raw SKILL.md: https://api.skillmd.com/api/skills/microsoft365dsc/review-changes/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: microsoft365dsc (https://skillmd.com/u/microsoft365dsc)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/microsoft365dsc/review-changes

---


# Review Changes

Perform a thorough, risk-aware code review using the knowledge graph.

## Steps

1. Run `detect_changes` to get risk-scored change analysis.
2. Run `get_affected_flows` to find impacted execution paths.
3. For each high-risk function, run `query_graph` with pattern="tests_for" to check test coverage.
4. Run `get_impact_radius` to understand the blast radius.
5. For any untested changes, suggest specific test cases.

## Output Format

Provide findings grouped by risk level (high/medium/low) with:

- What changed and why it matters
- Test coverage status
- Suggested improvements
- Overall merge recommendation

# Token Efficiency Rules

- ALWAYS start with `get_minimal_context(task="<your task>")` before any other graph tool.
- Use `detail_level="minimal"` on all calls. Only escalate to "standard" when minimal is insufficient.
- Target: complete any review/debug/refactor task in ≤5 tool calls and ≤800 total output tokens.