commit

Generate a conventional commit message from git diff --cached output.

1|1|Updated Mar 20, 2026
One-click install
npx skills add https://github.com/AKMofficial/CC-Setup --skill commit-akmofficial
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: commit
Source: https://github.com/AKMofficial/CC-Setup/tree/main/skills/commit
Command: npx skills add https://github.com/AKMofficial/CC-Setup --skill commit-akmofficial

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Writing conventional commit messages from just the diffs is error-prone and inconsistent; this skill automates generating a standardized message from staged changes.

Core Features & Use Cases

  • Generate a conventional commit message from git diff --cached output.
  • Write the message to COMMIT_MESSAGE.md in the project root.
  • Use case: after implementing a feature or fix, run the skill to produce a clean, ready-to-commit note for your team.

Quick Start

Run this skill when you have staged changes to generate a conventional commit message and save it to COMMIT_MESSAGE.md in the project root.

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 commit message from staged changes?

Generating a conventional commit message from staged changes involves reading the git diff --cached output and writing the standardized message to a file in your project root without executing a commit.

How do I write clean commit messages from git diff output?

Writing clean commit messages from git diff output requires analyzing the staged changes to produce a standardized note, which can be saved directly to a markdown file in the project root for review.

Can I prepare a commit message during a code review without committing?

Yes, you can prepare a commit message during a code review without committing by reading the staged changes and writing the final message to a markdown file, leaving the actual git commit execution separate.

Does the commit message generator work with git staged changes only?

The commit message generator works specifically with git staged changes by processing the git diff --cached output, meaning you must stage your files before generating the conventional commit note.

What is the best way to automate conventional commit messages for my workflow?

The best way to automate conventional commit messages for your workflow is to process the cached git diff output and save the generated text directly to a file in the project root for immediate use.