git-commit

Name: git-commit
Availability: InStock
Author: antoniocascais

Analyze staged changes and execute git commits with descriptive messages.

11|2|Updated Oct 1, 2025

Search Tags:#automation #git #workflow #commit #messages #version-control

Ready to run

npx skills add https://github.com/antoniocascais/claude-code-toolkit --skill git-commit-antoniocascais

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: git-commit
Source: https://github.com/antoniocascais/claude-code-toolkit/tree/main/skills/git-commit
Command: npx skills add https://github.com/antoniocascais/claude-code-toolkit --skill git-commit-antoniocascais

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill analyzes staged changes, proposes optimal commit structures (single or multiple), and generates descriptive messages with technical context, executing after user approval.

Core Features & Use Cases

Analyze staged changes to determine if a single atomic commit or multiple commits are needed.
Generate commit messages with an optional TICKET_ID prefix and a detailed body for future readers.
Execute commits after user confirmation, ensuring safe, intentional code changes.

Quick Start

Use this Skill in a repository with staged changes. Optionally provide a TICKET_ID to prefix messages, then review the proposed plan and approve to perform the commit.

Frequently Asked Questions about git-commit

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

FAQPage Schema

How do I generate descriptive git commit messages for staged changes?▼

To generate descriptive git commit messages, this Skill analyzes your staged changes and proposes an optimal commit structure with a detailed technical body. It determines whether a single atomic commit or multiple commits are needed before executing after your approval.

Can I automatically prefix commit messages with a TICKET_ID for version control?▼

Yes, you can prefix commit messages with a TICKET_ID for version control by providing the identifier when initiating the process. The generated commit messages will automatically include this prefix to maintain traceability with your project management system.

How do I split multiple staged changes into atomic git commits?▼

To split multiple staged changes into atomic git commits, this Skill analyzes the staged differences and proposes multiple commit structures. It evaluates whether the changes represent feature work, bug fixes, or refactors to separate them into logical, intentional commits.

What is the best way to plan and execute git commits safely?▼

The best way to plan and execute git commits safely is to analyze the staged changes and review a proposed commit plan before execution. This Skill generates a descriptive message and performs the final commit only after you explicitly approve the proposed structure.

Does this git commit automation tool work without external dependencies?▼

Yes, this git commit automation tool works without external dependencies. It operates independently to analyze your staged changes and generate commit messages, requiring only a repository with staged changes and an optional TICKET_ID to begin the workflow.