commit

Generate Conventional Commits messages by analyzing staged and unstaged Git changes.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/expeor/aws-automation --skill commit-expeor
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: commit
Source: https://github.com/expeor/aws-automation/tree/main/.claude/skills/commit
Command: npx skills add https://github.com/expeor/aws-automation --skill commit-expeor

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This tool ensures consistent, standardized commit messages by analyzing Git changes and automatically generating Conventional Commits messages.

Core Features & Use Cases

  • Analyze git changes (staged and unstaged) to determine the appropriate Conventional Commit type.
  • Suggest or apply commit messages according to Conventional Commits guidelines, including feat, fix, docs, chore, and more.
  • Integrate with common Git workflows, enabling --amend and --dry-run options to preview changes before committing.

Quick Start

Run the commit tool to automatically generate a Conventional Commit message for your latest changes.

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 changes?

To automatically generate conventional commit messages, you can use a tool that analyzes your staged and unstaged git changes to infer the appropriate commit type and scope from file paths. This standardizes messages without manual formatting effort.

What is the conventional commits format and how does it structure git history?

The conventional commits format structures git history by using standardized prefixes like feat, fix, docs, and chore. This standardized messaging enables clearer version control history and automates semantic versioning downstream.

Can I preview a conventional commit message before applying it to my git workflow?

Yes, you can preview a conventional commit message before applying it by using a dry-run option. This analyzes your git changes and outputs the suggested message without actually writing the commit to your version control history.

Does the commit automation tool support amending previous staged changes?

Yes, the commit automation tool supports amending previous staged changes. It integrates directly with common git workflows by offering an amend option to update your last commit with newly generated conventional messages.

How does automated commit tooling determine the scope for conventional commits?

Automated commit tooling determines the scope for conventional commits by analyzing the file paths of your staged and unstaged changes. It infers the affected component directly from your repository's directory structure.