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.
Profile →npx skills add ruvnet/ruflo --skill diff-analyze --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# 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__plugin_ruflo-core_ruflo__analyze_diff` with the diff content for a comprehensive analysis 2. **Risk score** — call `mcp__plugin_ruflo-core_ruflo__analyze_diff-risk` for a quantified risk assessment 3. **Classify changes** — call `mcp__plugin_ruflo-core_ruflo__analyze_diff-classify` to categorize (feature, bugfix, refactor, etc.) 4. **Get reviewers** — call `mcp__plugin_ruflo-core_ruflo__analyze_diff-reviewers` for recommended reviewers based on code ownership 5. **Diff stats** — call `mcp__plugin_ruflo-core_ruflo__analyze_diff-stats` for line counts, file counts, complexity metrics 6. **File-level risk** — call `mcp__plugin_ruflo-core_ruflo__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
- When to use
- Steps
- Risk factors
What does the diff-analyze skill do?
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.
How do I install it?
Run `npx skills add ruvnet/ruflo --skill diff-analyze --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From ruvnet/ruflo, a repository with 67,015 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.