Review changes
Finish with Proof: a portable execution protocol for coding agents—diagnose before patching, bound delegation, and verify real outcomes.
npx -y skills add MiaoY0uShan/FP --skill review-changesAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 2 stars2 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Perform a structured code review using change detection and impact
SKILL.md
1.1 KB, as published. Nobody here has run it
Review Changes
Perform a thorough, risk-aware code review using the knowledge graph.
Steps
- Run
detect_changes_toolto get risk-scored change analysis. - Run
get_affected_flows_toolto find impacted execution paths. - For each high-risk function, run
query_graph_toolwith pattern="tests_for" to check test coverage. - Run
get_impact_radius_toolto understand the blast radius. - 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.