commit

Create conventional git commit messages from working tree changes.

8|1|Updated Mar 1, 2026

Search Tags:#git #diff analysis #conventional commits #developer productivity #commit message #staged changes #repository workflow

Ready to run

npx skills add https://github.com/JoeCP17/LLM-Dot-files --skill commit-joecp17

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: commit
Source: https://github.com/JoeCP17/LLM-Dot-files/tree/main/claude/skills/commit
Command: npx skills add https://github.com/JoeCP17/LLM-Dot-files --skill commit-joecp17

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

You need to save your changes and communicate intent clearly, but writing conventional commit messages from diffs is time-consuming and easy to get wrong.

Core Features & Use Cases

Change Gathering: Collects current status, staged and unstaged diffs, and recent commit style references to inform the message.
Intent-Based Message Drafting: Determines the correct conventional commit type (feat, fix, refactor, docs, test, chore, perf, ci) based on what changed and why.
Safe Commit Execution: Prevents empty commits, avoids committing likely secrets by encouraging targeted staging, and verifies success after committing.

Quick Start

Tell the AI: commit the staged changes with a conventional commit message that matches the intent of the diff.

Frequently Asked Questions about commit

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

FAQPage Schema

How do I automatically generate conventional commit messages from git diff?▼

To generate conventional commit messages from git diff, the Skill analyzes staged and unstaged changes alongside recent commit history, then drafts an appropriate type like feat or fix based on the detected intent. It targets the correct conventional category by evaluating what changed and why.

What's the best way to write a conventional commit message from staged changes?▼

Writing a conventional commit message from staged changes requires analyzing the cached diff to determine the change type. This Skill automates that by running git diff --cached, selecting a type from feat, fix, refactor, docs, test, chore, perf, or ci, and describing the intent clearly.

Can I use natural language commands to commit git changes with a conventional format?▼

Yes, you can commit git changes using natural language commands like /commit, save changes, or 커밋. The Skill interprets these prompts, checks git status and diffs, stages changes safely, and executes the commit with a formatted conventional message.

How does a commit message generator handle empty commits or potential secrets?▼

A commit message generator handles empty commits and potential secrets by blocking empty commits entirely and encouraging targeted staging of specific files. It verifies success with git status after committing to ensure no unintended secrets are included.

When do I need to run git diff and git log before drafting a commit message?▼

You need to run git diff and git log before drafting a commit message when you want the new commit to match your repository's existing style. The Skill collects recent log references and current diffs to inform the correct conventional commit type and description.

Does this conventional commit tool work with both staged and unstaged repository workflows?▼

This conventional commit tool works with staged and unstaged repository workflows by running git diff and git diff --cached to gather changes. It stages changes safely before committing and verifies the final repository state with git status.