OpenParable
Skip to content
← Back to skills

Diff Analyze

Testing & Quality
diff-analyze

Diff Analyze is an Agent Skill for testing & quality published in the ruvnet/ruflo repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.

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.

View on GitHub ↗
QUICK START

How to use this skill

Bring this guide into your coding agent with a prompt tailored to the tool you use.

  1. Open your project in Codex.
  2. Copy and paste the prompt below.
  3. Review files and risks before approving any action.
Prompt to paste
Inspect the Agent Skill at https://github.com/ruvnet/ruflo/blob/HEAD/plugins/ruflo-jujutsu/skills/diff-analyze/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/diff-analyze, but wait for my approval before writing files or running scripts.

Copying this prompt does not install or run the skill. Review third-party files before use.

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