Skill Market

diff analyze

Analyze git diffs for risk scoring, reviewer recommendations, and change classification

GitHub
githubcommunityclaudemcp
0.0
0 installs73.4K GitHub starsby ruvnet

Skill Introduction

Overview
Analyze git diffs for risk scoring, reviewer recommendations, and change classification

Core value

Turns reusable Development know-how into an installable skill, helping users complete github, community, claude, mcp work faster.

Target users

  • Developers, testers, and maintainers who handle Development tasks in Focus Code.
  • Teams that already trust workflows or content from ruvnet.
  • Users who want standardized prompts, steps, or conventions instead of repeating setup work.

Best practices

  • Read the skill content first to confirm required inputs, expected outputs, and dependencies.
  • Try it on a small task before relying on it for critical work.
  • Add project-specific constraints such as coding style, target platform, test expectations, and delivery format.
  • For external sources, verify the source link, version, and recent maintenance activity.

Best use cases

  • Tasks related to github, community, claude, mcp that need a reusable execution flow.
  • Converting a community repo, team convention, or personal workflow into day-to-day assistance.
  • Starting from a proven skill instead of writing prompts or procedures from scratch.

Limits and boundaries

  • Results depend on the quality of the original skill content and may need human correction.
  • It does not replace code review, tests, security review, or professional judgment.
  • External tools, APIs, account permissions, and local dependencies still need separate setup.

Differentiation

  • Structured around Development, making it easier to discover and reuse than loose prompt snippets.
  • Marked as GitHub, which helps users judge trust and maintenance expectations.
  • Keeps the original source link available for repository, documentation, or discussion follow-up.
  • Tagged with github, community, claude, mcp, so it can be filtered by concrete task intent.

Install and use

Install
Copy Install Command
focus install diff-analyze-ecf758
View source

Detail Preview

SKILL.md

Primary filemarkdown2 KB

name: diff-analyze description: Analyze git diffs for risk scoring, reviewer recommendations, and change classification argument-hint: "[--branch BRANCH] [--pr PR#]" allowed-tools: mcp__claude-flow__analyze_diff mcp__claude-flow__analyze_diff-risk mcp__claude-flow__analyze_diff-classify mcp__claude-flow__analyze_diff-reviewers mcp__claude-flow__analyze_diff-stats mcp__claude-flow__analyze_file-risk Bash

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

Reviews

Overall rating

0.0
0.0

0 comments

No reviews yet