commit

Name: commit
Availability: InStock
Author: LarryHsiao

Generate conventional commit messages from git diffs and commit after approval.

Updated Mar 19, 2026

Search Tags:#git #commit #push #diff #approval #hook #message

Ready to run

npx skills add https://github.com/LarryHsiao/Skadi --skill commit-larryhsiao

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: commit
Source: https://github.com/LarryHsiao/Skadi/tree/main/skills/commit
Command: npx skills add https://github.com/LarryHsiao/Skadi --skill commit-larryhsiao

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the creation of clear, conventional commit messages from code changes and requires explicit user approval before the commit is made.

Core Features & Use Cases

Generate an imperative commit message from a diff and staged changes.
Pause for user approval before committing; supports --push to push after commit.
Integrates with existing Git hooks to preserve repository integrity.

Quick Start

Commit your current changes by generating a message, asking for approval, and performing the commit (push if requested).

Frequently Asked Questions about commit

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

FAQPage Schema

How do I generate a conventional git commit message from staged changes?▼

To generate a conventional git commit message, this Skill reads your git diff and status to produce an imperative message under 72 characters. It then prompts for your explicit approval before committing the changes.

Can I automatically push to my remote after generating a git commit?▼

Yes, you can automatically push after generating a git commit by using the --push option. Once you approve the generated commit message, the Skill performs the commit and immediately pushes the changes to your remote repository.

Does this git commit generator work with my existing Git hooks?▼

Yes, this git commit generator fully integrates with your existing Git hooks to preserve repository integrity. It generates the commit message and executes the commit while ensuring all your pre-commit and post-commit hooks remain active.

What is the best way to ensure my git commit messages follow conventional standards?▼

The best way to ensure conventional git commit messages is to enforce an imperative mood and a 72-character limit. This Skill automatically formats your message from the code diff to meet these standards before requesting approval.

Do I need to manually write commit messages when using this automation?▼

No, you do not need to manually write commit messages when using this automation. The Skill analyzes your git diff to generate the message, requiring only your approval to proceed with the commit and optional push.