skills.rest
vincent-kk
vincent-kkCOMMUNITY
Explore all skills by this author →
GitHub

git-change-analyzer

Aggregate Git commits, branch diffs, and staged changes into JSON.

1|Updated Nov 13, 2024
Search Tags:#git#analysis#json#diff#branch#changes
One-click install
npx skills add https://github.com/vincent-kk/albatrion --skill git-change-analyzer
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: git-change-analyzer
Source: https://github.com/vincent-kk/albatrion/tree/main/.claude/skills/git-change-analyzer
Command: npx skills add https://github.com/vincent-kk/albatrion --skill git-change-analyzer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the extraction and structuring of Git changes (commits, branch diffs, and staged modifications) into a consistent JSON format for auditing, reporting, or integration into CI workflows.

Core Features & Use Cases

  • Mode detection to select commit, branch, or staged analysis
  • Project context loading from .project-structure.yaml
  • Change collection using Git commands and structured data output
  • Supports monorepos and file-level classification for scalable reviews

Quick Start

Use the skill to analyze a specific commit, branch differences, or staged changes:

  • Analyze a commit: git-change-analyzer --commit <HASH>
  • Compare the current branch to base: git-change-analyzer --base master
  • Analyze staged changes: git-change-analyzer --staged

Frequently Asked Questions about git-change-analyzer

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

FAQPage Schema
How do I extract Git changes into JSON for CI workflows?▼

You can extract Git changes into JSON by running analysis modes for specific commits, branch diffs, or staged modifications. The tool aggregates and structures the data into a consistent JSON format suitable for auditing, reporting, or CI integration.

What is the best way to analyze branch differences in a monorepo?▼

To analyze branch differences in a monorepo, use the branch-diff analysis mode against a base branch like master. It supports monorepos by providing file-level classification for scalable review workflows.

Do I need a specific configuration file to analyze staged Git changes?▼

Yes, analyzing staged Git changes requires a project-context configuration file named .project-structure.yaml. The tool loads this context to properly aggregate and structure the staged modifications into JSON output.

Can I compare the current branch to a base branch and output the diff as JSON?▼

Yes, you can compare your current branch to a base branch and output the diff as JSON. By specifying the base branch, the tool collects the branch differences and structures them into a consistent JSON format.

Does this Git change analyzer work without any external dependencies?▼

The analyzer operates without external dependencies but requires standard Git tooling installed in your environment. It also relies on a .project-structure.yaml file to load the necessary project context for analysis.

Related Skills

Explore More Software Engineering Skills→
KiyorakaKiyoraka
368

auto-commit

Generate structured Git commit messages from code diffs and session context.

Community
Advanced
Firma-AIFirma-AI
106

review-rust-code

Reviews Rust code changes for correctness, robustness, documentation quality, and policy compliance.

Official
Advanced
stolinskistolinski
63

changeset

Create, propose, and apply Changesets for repository code changes.

Community
Advanced
LeeJuOhLeeJuOh
51

diff-visual

Visualize git diffs as interactive HTML reports with architecture diagrams and comparisons.

Community
Advanced