diff

Analyze git changes to classify modifications and assess impact and risk.

8|2|Updated Jul 18, 2025

Search Tags:#git #diff #risk-assessment #code-review #code-change #impact-analysis #semantic-analysis

Ready to run

npx skills add https://github.com/ConaryLabs/Mira --skill diff-conarylabs

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: diff
Source: https://github.com/ConaryLabs/Mira/tree/main/plugin/skills/diff
Command: npx skills add https://github.com/ConaryLabs/Mira --skill diff-conarylabs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps developers quickly understand the semantic impact of code changes by automatically classifying changes, identifying affected areas, and highlighting risk.

Core Features & Use Cases

Change Classification: Distinguish new, modified, deleted, and refactored elements.
Impact & Risk Analysis: Identify downstream callers, module dependencies, and potential ripple effects.
Use Case: Before merging a PR, run this Skill to summarize what changed and what might break.

Quick Start

Use the diff skill to analyze changes between two refs, for example: /mira:diff --from HEAD~1 --to HEAD The Skill will return a structured report with classifications, impacts, and risk.

Frequently Asked Questions about diff

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I assess the semantic impact of code changes before merging a pull request?▼

To assess semantic impact before merging, analyze git changes to classify modified elements, identify downstream callers, and highlight potential ripple effects. This provides structured risk insights and impact classification for code reviews.

What is semantic code change classification and how does it work for git diffs?▼

Semantic code change classification distinguishes new, modified, deleted, and refactored elements within git diffs. It works by running diffs between refs and producing structured output that evaluates impact and risk findings.

Can I analyze code changes and risks across mixed-language repositories?▼

Yes, you can analyze code changes and risks across mixed-language repositories. The analysis applies to code reviews, pull request evaluations, and post-commit analyses to identify module dependencies and potential ripple effects.

How do I run a semantic diff analysis between two git refs?▼

To run a semantic diff analysis between two git refs, execute a diff command specifying the source and target refs like HEAD~1 and HEAD. The tool returns a structured report with classifications, impacts, and risk findings.

What's the best way to identify downstream callers and module dependencies affected by a code change?▼

The best way to identify downstream callers and module dependencies is to perform an impact analysis on your git changes. This process highlights affected areas and potential ripple effects to evaluate risk before merging.