skills.rest
danbrickey
danbrickeyCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

commit-message

Generate conventional commit messages from staged git changes.

Updated Aug 27, 2026
Search Tags:#automation#git#workflow#commit#messages#version-control#conventional
One-click install
npx skills add https://github.com/danbrickey/exocortex --skill commit-message-danbrickey
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: commit-message
Source: https://github.com/danbrickey/exocortex/tree/main/shared/ai-resources/skills/commit-message
Command: npx skills add https://github.com/danbrickey/exocortex --skill commit-message-danbrickey

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill eliminates the guesswork and inconsistency in commit messages by generating conventional commit messages directly from your git changes.

Core Features & Use Cases

  • Analyze repository state: run git status, git diff, and git log to identify changes that will be committed.
  • Classify changes into conventional types (feat, fix, docs, style, refactor, test, chore) and optional scope for clarity.
  • Generate a complete commit message including subject, optional body, and footer, ready to copy into git and use in automation.

Quick Start

Run the skill after staging changes to generate a conventional commit message. Copy the output and run git commit -m "<generated message>" or integrate with a pre-commit hook for automatic message generation.

Frequently Asked Questions about commit-message

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

FAQPage Schema
How do I generate conventional commit messages from git changes?▼

To generate conventional commit messages from git changes, run the skill after staging your changes. It analyzes the repository state and outputs a formatted commit message ready to copy into git.

What types of conventional commits can be generated automatically?▼

Automatically generated conventional commits categorize changes into types like feat, fix, docs, style, refactor, test, and chore, enforcing the conventional commits structure with optional scope and description.

Can I include a body and footer in an automatically generated commit message?▼

Yes, the generated conventional commit message supports optional bodies and footers, providing detailed release notes alongside the standard subject line for comprehensive version-control tracking.

How do I analyze my repository state before writing a commit message?▼

Analyzing repository state involves running git status, git diff, and git log to identify staged changes. The skill handles this automatically to classify changes and generate the commit message.

Does this work with pre-commit hooks for automatic message generation?▼

Yes, you can integrate the generated output with a pre-commit hook for automatic message generation, streamlining the version-control workflow by removing manual message creation.

What is the best way to enforce a conventional commits structure in git?▼

The best way to enforce a conventional commits structure is to automatically generate the type, scope, and description from the current git diff, ensuring consistency and eliminating guesswork in commit messages.

Related Skills

Explore More Software Engineering Skills→
visualityplvisualitypl
4

ci_commit

Generate atomic git commits with imperative messages from staged changes.

Official
Intermediate
AndrewDrygaAndrewDryga
28

release

Create semantic version tags from changelogs and push them to Git.

Community
Advanced
AmidVoshakulAmidVoshakul

git-hooks-automation

Automate Git hook configuration for linting, formatting, and commit message validation.

Community
Advanced
plurigridplurigrid
60

changelog-generator

Generate user-facing changelogs from git commit history.

Official
Advanced