skills.rest
eveld
eveldCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

write-commit-message

Generate Conventional Commits messages and apply them via git commit.

10|2|Updated Dec 23, 2025
Search Tags:#git#workflow#development#commit#format#conventional-commits#message
One-click install
npx skills add https://github.com/eveld/claude --skill write-commit-message-eveld
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: write-commit-message
Source: https://github.com/eveld/claude/tree/main/skills/write-commit-message
Command: npx skills add https://github.com/eveld/claude --skill write-commit-message-eveld

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Inconsistent commit messages across a codebase are hard to read and audit; this skill enforces the Conventional Commits format to standardize every git commit.

Core Features & Use Cases

  • Enforces the Conventional Commits structure with type, optional scope, subject, and optional body and footer.
  • Validates subject length (72 characters) and uses imperative mood to ensure clear intent.
  • Integrates with Git workflows to generate ready-to-use commit payloads and apply them via a heredoc.

Quick Start

Ask the AI to generate a conventional commits compliant commit message for your staged changes and apply it with git commit.

Frequently Asked Questions about write-commit-message

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

FAQPage Schema
What is conventional commits format for git messages?▼

Conventional commits format standardizes git history by structuring messages with a type, optional scope, subject, and optional body and footer, ensuring consistent messaging across features, fixes, docs, and refactors.

How do I write a conventional commit message for staged git changes?▼

To write a conventional commit message, analyze your staged repository changes, validate the subject length and imperative mood, construct the payload, and apply it via a git commit heredoc.

Does conventional commits format require a specific subject length?▼

Conventional commits format requires a subject length of 72 characters or less. It also mandates using imperative mood to ensure clear intent for the git commit history.

Can I apply a conventional commit message directly using git commit?▼

Yes, you can apply conventional commit messages directly by constructing the payload with type, scope, subject, body, and footer, then passing it to the git commit command using a heredoc.

What is the best way to standardize git workflow commit history?▼

The best way to standardize git commit history is enforcing the conventional commits format, which validates subject tone and length to generate ready-to-use payloads for consistent messaging across all codebase changes.

When do I need to include a scope in my conventional commit?▼

You include an optional scope in a conventional commit to specify the module or component affected by the change, clarifying the context of features, fixes, docs, or refactors within the structured git message.

Related Skills

Explore More Software Engineering Skills→
naj2rnaj2r

commit

Creates git commits with auto-generated messages and optional push.

Community
Intermediate
FaysilAlshareefFaysilAlshareef
4

changelog-gen

Generate changelogs from git commits using Conventional Commits and Keep a Changelog formats.

Community
Intermediate
hidonguyenhidonguyen

ck:git

Automate git workflows for staging, committing, pushing, PR creation, and merging.

Community
Advanced
WarLikeLauxWarLikeLaux
10

commit-staged

Commit only staged Git changes with task ID-based messages.

Community
Intermediate