commit-messages

Generate conventional commit messages for staged changes with subject line rules.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This helps you craft clear, conventional commit messages that accurately describe code changes, reducing review time and improving repository history.

Core Features & Use Cases

  • Automatic type & scope: Suggests a conventional-commit style (feat, fix, docs) and identifies the affected area.
  • Quality checks: Enforces present tense, imperative mood, capitalization, and line length.
  • Use Case: When you stage multiple changes, generate a single, coherent commit message for release notes and history.

Quick Start

Generate a message for your staged changes with concise, descriptive content.

Frequently Asked Questions about commit-messages

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

FAQPage Schema
How do I generate conventional commit messages for staged git changes?

To generate conventional commit messages for staged git changes, this Skill analyzes your staged content and suggests an appropriate type and scope like feat or fix. It produces a single coherent message following standard subject line rules.

What are the rules for writing a good git commit subject line?

A good git commit subject line must use present tense, imperative mood, proper capitalization, and no trailing period, with a maximum of 50 characters. This Skill automatically enforces these quality checks on your generated messages.

Can I automatically add a Co-Authored-By footer to my commit messages?

Yes, you can automatically add a Co-Authored-By footer to your commit messages. The Skill includes this attribution footer in every generated message while suggesting the appropriate conventional-commit type and scope.

What is the best way to write release notes from multiple staged changes?

The best way to write release notes from multiple staged changes is to generate a single coherent conventional commit message. This Skill summarizes your staged content into a descriptive message suitable for repository history and release documentation.

Does this commit message generator support revising messages for already staged content?

Yes, this commit message generator supports revising messages for already staged content. It applies to typical workflows like committing fresh changes or updating existing staged content with clear conventional commit formatting.

Why should I use conventional commits for my code review process?

You should use conventional commits for your code review process because they reduce review time and improve repository history clarity. This Skill identifies the affected area and suggests accurate types to help reviewers understand changes quickly.