skills.rest
kscius
ksciusCOMMUNITY
Explore all skills by this author →
Website𝕏@ksciusGitHub

writing-commit-messages

Generate conventional commit messages with type prefixes, scopes, and formatting rules.

2|Updated Apr 3, 2026
Search Tags:#git#workflow#commit#conventional-commits#scopes#subject-line
One-click install
npx skills add https://github.com/kscius/KS-Cursor-Orchestrator --skill writing-commit-messages-kscius
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: writing-commit-messages
Source: https://github.com/kscius/KS-Cursor-Orchestrator/tree/main/skills/writing-commit-messages
Command: npx skills add https://github.com/kscius/KS-Cursor-Orchestrator --skill writing-commit-messages-kscius

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Writing conventional commit messages improves project history readability, makes code reviews easier, and supports automated release notes generation.

Core Features & Use Cases

  • Enforces the Conventional Commits format with types (feat, fix, refactor, docs, test, chore, perf, style, ci, revert) and optional scopes.
  • Validates subject lines to stay within ~50 characters and use imperative mood; provides examples and templates.
  • Guidance for composing bodies and footers, including breaking change notes and closes references for issues.
  • Use Case: When preparing a feature branch, generate a standardized commit message that clearly states the change and its impact.

Quick Start

Generate a conventional commit message for adding an OAuth login feature to the authentication module.

Frequently Asked Questions about writing-commit-messages

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

FAQPage Schema
How do I write conventional commit messages for git feature branches?▼

To write conventional commit messages, apply type prefixes like feat, fix, or docs, add optional scopes, and format the subject line in imperative mood under 50 characters. This ensures project history readability and supports automated release notes generation.

What is the correct format for a breaking change in conventional commits?▼

The correct format for a breaking change in conventional commits involves adding an exclamation mark after the type or scope, and detailing the change in the body or footer. This clearly flags modifications that break previous API or functionality expectations.

How do I structure git commit message bodies and footers for issue references?▼

Structure git commit message bodies by explaining what and why, separating footers with blank lines to include breaking change notes and closes references for issues. This maintains a clean, parseable history for code reviews and automated tooling.

What's the best way to generate a standardized commit message for a code refactor?▼

The best way to generate a standardized commit message for a code refactor is using the refactor type prefix with an optional scope. This clearly states the change and its impact without introducing new features or fixes to the codebase.

Does the conventional commits specification limit the subject line length?▼

Yes, the conventional commits specification limits the subject line length to roughly 50 characters. Adhering to this constraint while using imperative mood ensures your commit history remains concise, readable, and standardized across software development workflows.

Related Skills

Explore More Software Engineering Skills→
jk278jk278

git-analyzer

Analyze git repositories to summarize commit history and file changes.

Community
Intermediate
AstrumonAstrumon

changelog-generator

Generate Keep a Changelog entries from Conventional Commits history.

Community
Intermediate
mkittmkitt
6

git-standards

Enforce Git commit message and branch naming conventions.

Community
Basic
bismuthdigitalbismuthdigital

version

Analyzes code changes to update semantic version files and create Git tags.

Official
Advanced