commit

Generate conventional commit messages from staged Git changes.

Updated Feb 7, 2026
One-click install
npx skills add https://github.com/maggit/claude-workspace --skill commit-maggit
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: commit
Source: https://github.com/maggit/claude-workspace/tree/main/skills/commit
Command: npx skills add https://github.com/maggit/claude-workspace --skill commit-maggit

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps you create consistent, conventional commit messages for changes that have been staged, ensuring clear history and easier collaboration.

Core Features & Use Cases

  • Conventional-commit generation: Analyze staged changes and produce a properly formatted message with type, scope, and subject.
  • Automated committing: Optionally perform the commit with git to streamline the workflow.
  • Best practices: Enforces lowercase types, imperative mood, and a concise subject.

Quick Start

Create a conventional commit message for the currently staged changes and apply it with git commit.

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 for staged git changes?

To generate a conventional commit message, the Skill parses your git diff --cached output to analyze staged changes, automatically formats a message with the correct type, scope, and subject, and executes git commit -m to apply it.

What is the correct format for conventional commits in version control?

The conventional commit format requires a lowercase type (feature, fix, docs, refactor, test, chore), an optional scope, and a concise subject written in the imperative mood to ensure clear project history.

Can I automate git commit message generation for small to medium repositories?

Yes, you can automate git commit message generation for small-to-medium repositories by analyzing the staged Git index and automatically executing the commit with a formatted, rule-compliant message.

Does this commit message generator support feature, fix, and chore commit types?

This commit message generator supports typical git workflows with feature, fix, docs, refactor, test, and chore types, enforcing conventional-commit rules across your staged changes.

What's the best way to enforce imperative mood and lowercase types in git commits?

The best way to enforce imperative mood and lowercase types is to automatically parse the staged changes and generate a conventional commit message that strictly adheres to these formatting best practices before executing the commit.