diff-analyze
Analyze git diffs for risk scoring, reviewer recommendations, and change classification. Use when preparing a PR, reviewing a large or cross-module change, or before merging to assess risk and pick reviewers.
Install
npx skills add https://github.com/ruvnet/ruflo --skill diff-analyzeSKILL.md
Diff Analysis
Analyze git diffs for risk, complexity, and reviewer assignment.
When to use
Before submitting a PR or after making significant changes, analyze the diff to understand risk level, get reviewer recommendations, and classify the type of change.
Steps
- Analyze diff — call
mcp__plugin_ruflo-core_ruflo__analyze_diffwith the diff content for a comprehensive analysis - Risk score — call
mcp__plugin_ruflo-core_ruflo__analyze_diff-riskfor a quantified risk assessment - Classify changes — call
mcp__plugin_ruflo-core_ruflo__analyze_diff-classifyto categorize (feature, bugfix, refactor, etc.) - Get reviewers — call
mcp__plugin_ruflo-core_ruflo__analyze_diff-reviewersfor recommended reviewers based on code ownership - Diff stats — call
mcp__plugin_ruflo-core_ruflo__analyze_diff-statsfor line counts, file counts, complexity metrics - File-level risk — call
mcp__plugin_ruflo-core_ruflo__analyze_file-riskfor per-file risk breakdown
Risk factors
- Files with high churn history
- Security-sensitive paths (auth, crypto, permissions)
- Large diffs (>500 lines)
- Cross-module changes
- Database migration files
Related skills
improve-codebase-architecturemattpocock1MScan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick.codebase-designmattpocock691KShared vocabulary for designing deep modules. Use when the user wants to design or improve a module's interface, find deepening opportunities, decide where a seam goes, make code more testable or AI-navigable, or when another skill needs the deep-module vocabulary.web-design-guidelinesvercel-labs676KReview UI code for Web Interface Guidelines compliance. Use when asked to "review my UI", "check accessibility", "audit design", "review UX", or "check my site against best practices".code-reviewmattpocock631KReview the changes since a fixed point (commit, branch, tag, or merge-base) along two axes: Standards (does the code follow this repo's documented coding standards?) and Spec (does the code match what the originating issue/spec asked for?). Runs both reviews in parallel sub-agents and reports them side by side. Use when the user wants to review a branch, a PR, work-in-progress changes, or asks to \"review since X\".