commit

Generate git commit messages following the Conventional Commits specification.

7|Updated Dec 17, 2025
One-click install
npx skills add https://github.com/nweii/agent-stuff --skill commit-nweii
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: commit
Source: https://github.com/nweii/agent-stuff/tree/main/skills/commit
Command: npx skills add https://github.com/nweii/agent-stuff --skill commit-nweii

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Create well-formatted git commits following Conventional Commits to improve traceability and maintainability of code changes.

Core Features & Use Cases

  • Enforces a concise, imperative subject line and an optional body detailing the change.
  • Supports conventional types (feat, fix, docs, style, refactor, perf, test, chore) and optional scope.
  • Provides guidance for writing clear messages and marking breaking changes.

Quick Start

Provide a concise, conventional commit message for the current change, e.g., feat(auth): add OAuth2 login support.

Frequently Asked Questions about commit

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

FAQPage Schema
How do I write a conventional commit message for git?

To write a conventional commit message, you provide a concise, imperative subject line with an optional body. The Skill automates this by structuring your changes into types like feat, fix, or docs, along with an optional scope.

What is the conventional commits specification and when do I need it?

The conventional commits specification is a standardized format for git commit messages that improves traceability and maintainability. You need it in software development workflows requiring consistent commit history across features, bug fixes, and maintenance tasks.

How do I format a breaking change in a conventional commit?

To format a breaking change in a conventional commit, you follow the specification's guidance for marking breaking changes within the message structure. This Skill provides explicit guidance to ensure breaking changes are noted correctly alongside the subject and body.

Can I include a scope in my git commit message?

Yes, you can include an optional scope in your git commit message. This Skill supports conventional types such as feat, fix, docs, and refactor, allowing you to append a scope like feat(auth) to categorize changes within specific modules.

What is the best way to automate consistent git commit messages?

The best way to automate consistent git commit messages is by enforcing a well-formatted structure with an imperative subject line and detailed body. This Skill satisfies subject length requirements and body explanations to maintain a uniform commit history.

Are there limitations on subject length for conventional commits?

Yes, conventional commits require a concise subject line to maintain readability. This Skill enforces subject length constraints and provides guidance for writing clear, imperative statements without exceeding the standard character limits.