git-commit

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.

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.

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.

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.

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.