Diff Analyze
- 652 installs
- 67k repo stars
- Updated August 4, 2026
- ruvnet/ruflo
diff-analyze is an agent skill that analyzes git diffs for risk scoring, change classification, and reviewer recommendations via claude-flow MCP tools before pull request submission.
About
diff-analyze is a ruvnet ruflo skill that inspects git diffs before commits or pull requests using six claude-flow MCP analyze tools: analyze_diff, analyze_diff-risk, analyze_diff-classify, analyze_diff-reviewers, analyze_diff-stats, and analyze_file-risk. Developers invoke it when preparing large or cross-module PRs, assessing merge risk, or picking appropriate reviewers. Optional arguments include `--branch BRANCH` and `--pr PR#` for targeted analysis. The skill also permits Bash for local git context. Outputs include risk scores, change classifications, reviewer suggestions, and per-file risk breakdowns so teams catch high-impact diffs early instead of discovering issues in late review.
- Analyzes git diffs to surface meaningful changes and impact
- Generates structured summaries, risk assessments, and suggestions
- Works with any agent workflow that produces code changes
- Reduces review time by turning raw diffs into actionable reports
- Supports both local and remote repository analysis modes
Diff Analyze by the numbers
- 652 all-time installs (skills.sh)
- +10 installs in the week ending Jul 26, 2026 (Skillselion tracking)
- Ranked #204 of 1,352 Code Review & Quality skills by installs in the Skillselion catalog
- Data as of Aug 5, 2026 (Skillselion catalog sync)
npx skills add https://github.com/ruvnet/ruflo --skill diff-analyzeAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 652 |
|---|---|
| repo stars | ★ 67k |
| Last updated | August 4, 2026 |
| Repository | ruvnet/ruflo ↗ |
How do you score git diff risk before merging?
Automatically analyze code diffs and generate structured insights before committing or creating pull requests.
Who is it for?
Developers preparing large or cross-module pull requests who need structured risk assessment before merge.
Skip if: Pre-commit lint-only checks or test-gap analysis without any git diff review requirement.
When should I use this skill?
The user prepares a PR, reviews a large diff, or asks for risk scoring and reviewer recommendations on git changes.
What you get
Risk scores, change classifications, reviewer recommendations, diff stats, and per-file risk reports.
- diff risk score report
- change classification summary
- reviewer recommendation list
By the numbers
- Integrates 6 claude-flow MCP analyze_diff tools
- Accepts --branch and --pr optional arguments for scoped analysis
Files
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
1. Analyze diff — call mcp__claude-flow__analyze_diff with the diff content for a comprehensive analysis 2. Risk score — call mcp__claude-flow__analyze_diff-risk for a quantified risk assessment 3. Classify changes — call mcp__claude-flow__analyze_diff-classify to categorize (feature, bugfix, refactor, etc.) 4. Get reviewers — call mcp__claude-flow__analyze_diff-reviewers for recommended reviewers based on code ownership 5. Diff stats — call mcp__claude-flow__analyze_diff-stats for line counts, file counts, complexity metrics 6. File-level risk — call mcp__claude-flow__analyze_file-risk for 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 ArchitectureSafely deepen clusters of shallow modules into cohesive, testable units while respecting their external dependencies.566k196k
Caveman ReviewGet ultra-compressed, one-line code review comments that cut noise while keeping every actionable fix.270k94.7kCodebase DesignShared vocabulary for designing deep modules: improve a module's interface, find deepening opportunities, decide where a seam goes, make code more testable.266k196kCavecrewDelegate coding tasks to specialized subagents that return compressed output, keeping the main context window usable for much longer sessions.220k94.7kCode ReviewReviews a branch or PR diff on two axes at once: conformance to coding standards plus a code-smell baseline, and whether it actually implements the original spec.201k196k
Requesting Code ReviewDispatch a consistent, high-signal code reviewer subagent that catches plan deviations and quality issues before merging or continuing development.183k264kHow it compares
Pick diff-analyze over manual PR description writing when structured risk scoring and reviewer routing matter for large diffs.
FAQ
Which MCP tools does diff-analyze use?
diff-analyze calls six claude-flow MCP tools: analyze_diff, analyze_diff-risk, analyze_diff-classify, analyze_diff-reviewers, analyze_diff-stats, and analyze_file-risk for structured pre-PR analysis.
When should diff-analyze run?
diff-analyze runs before submitting a pull request or after significant cross-module changes. Use it to assess merge risk, classify changes, and recommend reviewers before code review begins.