commit

Create Conventional Commits messages from git status and diffs.

2|Updated Jan 22, 2026
One-click install
npx skills add https://github.com/abnegate/claudes --skill commit-abnegate
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: commit
Source: https://github.com/abnegate/claudes/tree/main/skills/commit
Command: npx skills add https://github.com/abnegate/claudes --skill commit-abnegate

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It solves the problem of inconsistent, poorly formatted commit messages by generating a Conventional Commits style message that matches the changes you’re making.

Core Features & Use Cases

  • Conventional Commits formatting: Produces commit messages in the required (<type>): <description> format with no body or co-authors.
  • Automatic type selection: Picks an appropriate type (feat, fix, refactor, docs, test, chore, perf, style) based on the detected changes when no message is provided.
  • Safe commit workflow: Inspects current changes before staging/committing, and applies safety rules to avoid credential/secret files and risky git options.

Quick Start

Run the commit skill with the message you want, or omit the message and let it infer the correct conventional commit type from your current git changes.

Frequently Asked Questions about commit

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

FAQPage Schema
How do I create conventional commits automatically from my staged git changes?

To create conventional commits automatically, this skill inspects your git status and diffs to select an appropriate commit type like feat or fix, stages relevant files with git add, and creates the commit using a heredoc template.

What is the conventional commits format for writing git commit messages?

The conventional commits format structures git commit messages as <type>: <description>, using types like feat, fix, refactor, docs, test, chore, perf, or style to categorize the changes made in the repository.

Can I automatically detect the correct commit type from my git diff analysis?

You can automatically detect the commit type through git diff analysis; when no message is provided, the skill evaluates current changes to pick the most appropriate conventional commits type for your update.

How do I prevent committing secret files when staging git changes?

To prevent committing secret files during staging, the workflow applies safety rules that inspect changes beforehand, avoiding credential files and blocking risky git options from being included in the commit.

What is the best way to enforce consistent git workflow commit standards across a team?

The best way to enforce consistent git workflow commit standards is generating conventional commits messages that match intended change types, ensuring uniform formatting across everyday development commits and pre-PR grouping.

Does this commit workflow support custom messages or does it only auto-generate them?

The commit workflow supports custom messages; you can provide specific arguments to use as the commit message, or omit them entirely to let the skill infer the correct conventional commit type from your current git changes.