skills.rest
marchatton
marchattonCOMMUNITY
Explore all skills by this author →
Website𝕏@marchattonhereGitHub

commit

Generate Git commit messages following the Conventional Commits specification.

5|Updated Oct 22, 2025
Search Tags:#git#developer tools#version control#commit#conventional commits#code history
One-click install
npx skills add https://github.com/marchatton/agent-skills --skill commit-marchatton
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: commit
Source: https://github.com/marchatton/agent-skills/tree/main/.agents/skills/00-utilities/commit
Command: npx skills add https://github.com/marchatton/agent-skills --skill commit-marchatton

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps you write clear, consistent, and conventional Git commit messages, improving code history readability and automation.

Core Features & Use Cases

  • Conventional Commits: Enforces the Conventional Commits specification for commit messages.
  • Structured Commit Messages: Guides users to include type, scope, and a descriptive subject.
  • Use Case: When you fix a bug in the authentication module, you can use this skill to generate a commit message like fix(auth): use hmac.compare_digest for secure comparison.

Quick Start

Use the commit skill to create a git commit with the message "feat(api): add user profile endpoint".

Frequently Asked Questions about commit

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

FAQPage Schema
How do I write conventional Git commits with type, scope, and subject?▼

Conventional Git commits require structuring messages with a type, scope, and subject like `fix(auth): use hmac.compare_digest`. This specification improves code history readability and enables automated changelog generation.

What is the Conventional Commits specification for code history?▼

The Conventional Commits specification standardizes commit messages by enforcing a structured format including type, scope, and subject. This creates a clear code history and facilitates automated changelog generation for version control.

How do I format breaking changes and trailers in a Git commit message?▼

Formatting breaking changes and trailers in a Git commit message involves adding specific indicators and structured metadata to your conventional commit body. This supports complex commits while maintaining the specification for automated processing.

Can I use conventional commits for automated changelog generation?▼

Yes, conventional commits enable automated changelog generation. By adhering to the specification with structured types and scopes, your Git commit history becomes machine-readable for automated changelog creation and version control.

Does the conventional commit format support complex commits with bodies?▼

Yes, the conventional commit format supports complex commits with bodies, trailers, and breaking change indicators. This allows you to provide detailed context beyond the basic type, scope, and subject structure.

Related Skills

Explore More Software Engineering Skills→
jk278jk278

git-analyzer

Analyze git repositories to summarize commit history and file changes.

Community
Intermediate
FaysilAlshareefFaysilAlshareef
4

changelog-gen

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

Community
Intermediate
t0labt0lab
2

git-conventional

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

Official
Basic
MileniumTickMileniumTick

conventional-commit

Generate XML-structured Conventional Commit messages for Git commits.

Community
Advanced