skills.rest
PVPha
PVPhaCOMMUNITY
Explore all skills by this author →
GitHub

commit-messages

Generate conventional commit messages with optional Gitmojis, scopes, bodies, and footers.

Updated Feb 13, 2026
Search Tags:#git#version control#commit#conventional commits#code history#gitmoji
One-click install
npx skills add https://github.com/PVPha/agent_skills --skill commit-messages-pvpha
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: commit-messages
Source: https://github.com/PVPha/agent_skills/tree/main/skills/commit-messages
Command: npx skills add https://github.com/PVPha/agent_skills --skill commit-messages-pvpha

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps you write clear, consistent, and informative commit messages that adhere to the Conventional Commits specification, improving code history and collaboration.

Core Features & Use Cases

  • Conventional Commits: Generates commit messages following the <type>(<scope>): <subject> format.
  • Gitmoji Integration: Optionally includes relevant Gitmojis for visual context.
  • Detailed Guidance: Provides explanations for commit types, scopes, bodies, and footers.
  • Use Case: When you finish a new feature, use this Skill to generate a commit message like ✨ feat(auth): implement password reset flow with an optional body explaining the changes and closing related issues.

Quick Start

Use the commit-messages skill to write a commit message for a new feature that adds user authentication.

Frequently Asked Questions about 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 version control?▼

Conventional commit messages follow the `<type>(<scope>): <subject>` format, enforcing imperative mood and character limits for clear code history. You can include optional scopes, bodies, and footers to provide detailed context for software development changes.

What are conventional commits and when should I use them?▼

Conventional commits are a structured formatting specification for git version control, using types, scopes, and subjects. You should use them to facilitate consistent code history, improve collaboration, and enable automation in software development projects.

Can I include gitmoji in my conventional commit messages?▼

Yes, you can include gitmoji in conventional commit messages to add visual context. This integration optionally prepends relevant emojis, such as `✨ feat(auth): implement password reset flow`, alongside the standard type, scope, and subject structure.

What is the best way to structure a git commit body and footer?▼

The best way to structure a git commit body and footer is to use them for detailed explanations and metadata like closing related issues. The body provides context about the changes, while the footer typically references issues, ensuring structured formatting for clarity and automation.

Why does my git commit message need to be in imperative mood?▼

Your git commit message needs to be in imperative mood to enforce structured formatting and consistency. This practice matches the inherent behavior of git itself and ensures clarity when generating conventional commit messages for automated processing and code history tracking.

Related Skills

Explore More Software Engineering Skills→
tomlupotomlupo

generating-commit-messages

Generate structured Git commit messages from staged changes.

Community
Basic
t0labt0lab
2

git-conventional

Enforce Conventional Commits formatting and map commit types to semantic version bumps.

Official
Basic
ksopylaksopyla

git-workflow

Enforce Git workflow conventions for branch naming, commit messages, and pull requests.

Community
Intermediate
kevinrobaynakevinrobayna

commit

Generate conventional Git commit messages from analyzed code changes.

Community
Intermediate