mcpField
D
diff-analyze

diff-analyze

github.com/ruvnetTesting & quality80.0k751 installsUpdated today
Repository

About diff-analyze

A workflow for reviewing Git diffs before a pull request or after substantial changes. It assesses risk and complexity, classifies changes, and suggests reviewers based on code ownership.

Key features

  1. 01Comprehensive diff analysis
  2. 02Quantified risk assessment
  3. 03Change type classification
  4. 04Reviewer recommendations
  5. 05Diff and complexity statistics
  6. 06Per-file risk breakdown

Use cases

  1. 01Assessing a diff before submitting a pull request
  2. 02Identifying high-risk files in a large change
  3. 03Finding reviewers based on code ownership

MCP support

Uses Ruflo MCP tools to analyze diffs, calculate risk, classify changes, recommend reviewers, and report statistics.

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/ruvnet/ruflo --skill diff-analyze

After installing, type/diff-analyzein Claude Code to confirm it loaded.

Details

From the project README

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

Comments

Markdown supported