skills.rest
kapilvirenahuja
kapilvirenahujaCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

analyze-changes

Analyze uncommitted Git changes into categorized, issue-grouped summaries with risk assessment.

3|Updated Jan 25, 2026
Search Tags:#git#breaking changes#risk assessment#change analysis#sensitive files#issue grouping#diff parsing
One-click install
npx skills add https://github.com/kapilvirenahuja/garura --skill analyze-changes
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: analyze-changes
Source: https://github.com/kapilvirenahuja/garura/tree/main/core/components/skills/analyze-changes
Command: npx skills add https://github.com/kapilvirenahuja/garura --skill analyze-changes

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

It turns unclear, uncommitted code changes into structured, risk-aware analysis so the next agent step is informed and safe.

Core Features & Use Cases

  • Change summarization: Captures staged, unstaged, untracked, and diff statistics for quick situational awareness.
  • Issue-based grouping: Groups changes primarily by extracted issue number (from branch naming), avoiding misleading splits by directory.
  • Risk detection: Flags sensitive files and likely breaking-change indicators using repository-standard patterns.

Quick Start

Ask an agent to analyze the current working tree changes to produce a grouped, risk-aware analysis report for the calling workflow.

Frequently Asked Questions about analyze-changes

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

FAQPage Schema
How do I analyze uncommitted Git changes for breaking change risks?▼

To assess uncommitted Git changes for risk, the analysis groups diffs by extracted issue number and flags sensitive files or breaking-change indicators. It reads repository standards to generate a categorized summary for informed workflow decisions.

What is the best way to group Git diffs by issue number for a code review?▼

Grouping Git diffs by issue number is best handled by extracting identifiers from branch naming conventions. This prevents misleading directory-based splits and provides structured context for checkpointing or review processes.

Does this change analysis approach require specific repository configuration files?▼

Yes, the change analysis requires risk and categorization standards to be defined in repository files. It reads these configurations to accurately detect sensitive files and apply breaking-change indicators during the diff parsing process.

Can I capture staged, unstaged, and untracked Git files in one summary?▼

Yes, you can capture staged, unstaged, and untracked Git files alongside diff statistics in a single summary. This provides comprehensive situational awareness of the entire working tree before proceeding with commits.

When should I not use automated diff parsing for risk assessment?▼

Automated diff parsing for risk assessment should not be used when repository files lack defined risk and categorization standards. Without these configuration patterns, the tool cannot accurately detect sensitive files or breaking-change indicators.

Related Skills

Explore More Software Engineering Skills→
mhattingpetemhattingpete
657

git-pushing

Stage, commit, and push code changes with conventional commit messages.

Community
Basic
marchattonmarchatton
5

commit

Generate Git commit messages following the Conventional Commits specification.

Community
Intermediate
wiltaylorwiltaylor

review-pr

Generate structured JSON feedback from pull request diffs.

Community
Intermediate
rauly-1408rauly-1408

differential-review

Review code changes for security regressions and generate markdown reports.

Community
Advanced