collect-commit-info

Collect staged file and diff metadata to generate conventional commit specifications.

Updated Dec 6, 2025
One-click install
npx skills add https://github.com/reedom/claude-code-commands --skill collect-commit-info
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: collect-commit-info
Source: https://github.com/reedom/claude-code-commands/tree/main/git/skills/collect-commit-info
Command: npx skills add https://github.com/reedom/claude-code-commands --skill collect-commit-info

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Analyzes staged files and diffs to propose conventional commit specs.

Core Features & Use Cases

  • Groups staged changes by category
  • Generates conventional commit messages
  • Returns JSON specs for caller to execute

Quick Start

Run the collect-info.sh script to generate commit specs from staged changes.

Frequently Asked Questions about collect-commit-info

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

FAQPage Schema
How do I generate conventional commit messages from staged changes?

Conventional commit messages summarize staged changes by grouping files by type and generating structured messages that follow the conventional commits specification. Run the collect-info.sh script on your Git repository to automatically analyze staged diffs and produce commit specs in JSON format, including per-group messages and intended impact.

What types of changes can this analyze in a commit?

This analyzes staged changes across dependencies, CI configurations, config files, source code, tests, and documentation. It groups these by category, identifies the scope of each change, and generates conventional commit specifications that reflect the intended impact of each modification.

Can I use this during pre-commit workflows?

Yes, this Skill is designed for pre-commit and review workflows. It collects metadata of staged files and diffs during the pre-commit phase to produce conventional commit specifications that you can execute before finalizing your commits.

What output format does this produce?

This returns JSON containing a commits array and summary. Each commit entry details the grouped message, affected files, and intended impact according to Conventional Commits, allowing you to review or programmatically execute the proposed commit structure.

Do I need to manually write commit messages after running this?

No, this generates conventional commit specifications automatically from your staged changes. The JSON output provides ready-to-use commit messages and file groupings, eliminating manual message writing for pre-commit automation.