skills.rest
dhofheinz
dhofheinzCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

Message Generation Skill

Generate conventional Git commit messages with subject, body, and footer.

9|2|Updated Oct 13, 2025
Search Tags:#version control#validation#message generation#commit message#git commit#commit footer#commit body#subject line
One-click install
npx skills add https://github.com/dhofheinz/open-plugins --skill message-generation-skill
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: Message Generation Skill
Source: https://github.com/dhofheinz/open-plugins/tree/main/plugins/git-commit-assistant/commands/message-generation
Command: npx skills add https://github.com/dhofheinz/open-plugins --skill message-generation-skill

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Writing clear, concise, and conventional Git commit messages is often overlooked but is vital for project history and collaboration. This skill automates the generation and validation of commit messages, ensuring they follow best practices, including subject lines, body content, and footers, saving you time and improving communication.

Core Features & Use Cases

  • Subject Generation: Creates concise and informative subject lines based on your changes, adhering to conventions.
  • Body Composition: Helps write detailed and contextual commit body content, providing necessary background for reviewers.
  • Footer Addition: Adds conventional footers (e.g., Co-authored-by, Fixes #), linking commits to issues or collaborators.
  • Message Validation: Checks the generated message against project conventions, ensuring consistency across the team.
  • Use Case: A developer has staged changes and needs a good commit message. They use this skill to generate a subject line based on the changes, then compose a detailed body, and finally add a Fixes # footer, ensuring a professional and informative commit message that aids in project tracking.

Quick Start

Use the message-generation skill to generate a subject line for the current staged changes.

Frequently Asked Questions about Message Generation Skill

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

FAQPage Schema
How do I generate conventional commit messages that follow Git best practices?▼

Conventional commit messages follow a structured format with subject line (50 characters max, imperative mood), body (72-character line wrap), and footer (issue references, breaking changes). This Skill generates each component automatically, ensuring consistency across your project's Git history.

What should a Git commit message subject line include?▼

A subject line should be concise, imperative, and lowercase after the colon, with no trailing period—maximum 50 characters. This Skill creates subject lines based on your staged changes, deriving details from modified files to produce clear, searchable commit history.

Can I validate my commit messages against Conventional Commits standards?▼

Yes. This Skill validates complete commit messages against Conventional Commits requirements, checking imperative mood, line length, formatting, and footer syntax. Validation catches inconsistencies before they enter your repository.

How do I add footers like issue references and co-author details to commit messages?▼

Conventional footers link commits to issues, collaborators, and breaking changes using syntax like `Fixes #123` or `Co-authored-by`. This Skill appends footers automatically, integrating issue tracking and team attribution into your commit workflow.

Why does commit message formatting matter for version control workflows?▼

Structured commit messages enable automated changelog generation, cleaner project history, and faster code review. Enforcing Conventional Commits across your team improves collaboration and makes Git history queryable and maintainable.

Can this work across different software projects with different commit conventions?▼

This Skill is built for projects enforcing Conventional Commits specifically. It routes tasks to dedicated handlers for subject, body, footer, validation, and completion, applying consistent technical requirements across all software project types.

Related Skills

Explore More Software Engineering Skills→
richardcbrichardcb
15

git-commit

Generate conventional commit messages from staged Git changes.

Community
Intermediate
NodeJSmithNodeJSmith
1

mine.commit-push

Stage changes, generate commit messages, update changelogs, and push to Git.

Community
Advanced
DanomanicDanomanic

conventional-commits

Enforce conventional commit formatting for git commit messages.

Community
Basic
zhangzhang-111-izhangzhang-111-i
2

changelog-generator

Generate changelog entries from Conventional Commits in markdown or JSON.

Community
Intermediate