ase-meta-diff

Summarize staged Git changes into intent-grouped narratives with risk assessment.

44|5|Updated Apr 6, 2026
One-click install
npx skills add https://github.com/rse/ase --skill ase-meta-diff
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ase-meta-diff
Source: https://github.com/rse/ase/tree/main/plugin/skills/ase-meta-diff
Command: npx skills add https://github.com/rse/ase --skill ase-meta-diff

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires git, grep, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill turns raw Git diffs into a concise, human-readable narrative of what changed and why, grouped by intent.

Core Features & Use Cases

  • Diff Summarization: Summarize staged Git changes into a narrative, grouped by intent (Feature, Improvement, Bugfix, etc.).
  • Coherence Check: Optionally check for intent coherence and flag hunks that do not serve the intended change.
  • Risk Assessment: Optionally score the diff against a risk rubric and emit a graded risk report.
  • Blast Radius Map: Optionally render a blast-radius map showing the impact of changes on the codebase.

Quick Start

Summarize the currently staged changes with ase-meta-diff.

Frequently Asked Questions about ase-meta-diff

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

FAQPage Schema
How do I summarize Git changes grouped by intent for code review?

Summarize staged Git changes grouped by intent by running the tool against your current diff. It generates a concise, human-readable narrative categorizing code changes into Feature, Improvement, or Bugfix groupings for review.

Can I check if my Git diff hunks serve the intended change?

Yes, you can check Git diff coherence by enabling the coherence check option. It evaluates staged changes against the identified intent and flags specific hunks that do not align with the intended change purpose.

What is the best way to assess risk and change impact from a Git diff?

Assess risk and change impact from a Git diff by applying the risk assessment and blast-radius map options. It scores the diff against a risk rubric and renders a map showing the codebase impact.

Do I need git and grep installed to analyze staged changes?

Yes, you need both git and grep installed to analyze staged changes. These dependencies are required for the tool to parse repository diffs and perform the internal codebase analysis for coherence and risk assessment.

Why does my code review summary include incoherent hunks?

Code review summaries include incoherent hunks when the coherence check is not enabled. Running the coherence check explicitly flags hunks that do not serve the intended change, separating aligned changes from outliers.