skills.rest
drseanwing
drseanwingCOMMUNITY
Explore all skills by this author →
GitHub

commit

Create conventional git commits with enforced type, scope, and subject formats.

Updated Aug 27, 2026
Search Tags:#git#commit#scope#conventional-commits#type#subject#trailers
One-click install
npx skills add https://github.com/drseanwing/Pipelines --skill commit-drseanwing
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: commit
Source: https://github.com/drseanwing/Pipelines/tree/main/apps/ralph/skills/commit
Command: npx skills add https://github.com/drseanwing/Pipelines --skill commit-drseanwing

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Standardizes commit messages to improve readability, changelogs, and traceability by ensuring each commit follows Conventional Commits with a structured type, scope, and subject.

Core Features & Use Cases

  • Enforces Conventional Commits format with a mandatory type and scope.
  • Supports common commit types such as feat, fix, refactor, perf, test, ci, docs, chore, style, and security.
  • Requires a kebab-case scope and a concise subject line (max 50 characters) with present-tense wording.
  • Provides guidance for including an optional body and trailers to describe changes in detail and link issues.
  • Core workflow covers reviewing changes, staging files, composing a properly formatted commit, and verifying the latest commit.
  • Use case: standardize commit history across a team to improve changelogs and release notes.

Quick Start

Stage changes with git add <files> and commit using a type(scope): subject message, for example git commit -m 'feat(auth): add login flow'.

Frequently Asked Questions about commit

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

FAQPage Schema
How do I write conventional commits with a scope and subject?▼

Conventional commits require a structured format: type(scope): subject. You must use a valid type like feat or fix, a kebab-case scope, and a concise present-tense subject line limited to 50 characters.

What conventional commit types should I use for my git history?▼

Valid conventional commit types include feat, fix, refactor, perf, test, ci, docs, chore, style, and security. Selecting the correct type standardizes commit history and improves traceability across development teams.

How do I add a body and trailers to a conventional commit message?▼

To add a body and trailers to a conventional commit, include an optional body for detailed change descriptions followed by trailers to link issues. This provides context beyond the 50-character subject limit.

Can I use conventional commits to standardize my team's changelog generation?▼

Yes, standardizing commit messages with conventional commits improves readability and traceability. Enforcing a structured type, scope, and subject format directly supports automated changelog generation and release notes.

Why does my conventional commit subject line fail validation?▼

Your conventional commit subject line fails validation if it exceeds the 50-character limit, lacks present-tense wording, or omits the mandatory type and kebab-case scope. Enforced structure rules require strict adherence to formatting.

Related Skills

Explore More Software Engineering Skills→
AKMofficialAKMofficial
1

commit

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

Community
Intermediate
plurigridplurigrid
60

changelog-generator

Generate user-facing changelogs from git commit history.

Official
Advanced
ACuberoACubero

git-workflow

Guide Git workflows with conventional commits, branching strategies, and pre-commit hooks.

Community
Intermediate
axone-protocolaxone-protocol
124

conventional-commits

Enforce Conventional Commits structure for commit messages.

Official
Intermediate