skills.rest
wizact
wizactCOMMUNITY
Explore all skills by this author →
Website𝕏@amirmohtasebiGitHub

generate-commit-message

Generate Git commit messages following the Conventional Commits specification.

1|Updated Oct 18, 2025
Search Tags:#code quality#git#developer tools#version control#conventional commits#commit message
One-click install
npx skills add https://github.com/wizact/dotclaude --skill generate-commit-message-wizact
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: generate-commit-message
Source: https://github.com/wizact/dotclaude/tree/main/wizact-marketplace/plugins/wizact-dev-essentials/skills/generate-commit-message
Command: npx skills add https://github.com/wizact/dotclaude --skill generate-commit-message-wizact

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill automates the generation of Git commit messages, ensuring they adhere to the Conventional Commits standard and best practices, making your commit history clear and informative.

Core Features & Use Cases

  • Conventional Commits Generation: Automatically creates commit messages with appropriate types (feat, fix, docs, etc.), scopes, and descriptions.
  • Best Practice Enforcement: Guides users on imperative mood, subject line length, body wrapping, and issue referencing.
  • Use Case: After making changes to the user authentication module, invoke this skill to generate a commit message like feat(auth): Implement JWT-based login with a detailed body explaining the changes and referencing the related issue.

Quick Start

Use the generate-commit-message skill to create a commit message for your recent changes.

Frequently Asked Questions about generate-commit-message

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

FAQPage Schema
How do I generate a conventional commit message from a git diff?▼

The best way to write git commit messages is to enforce imperative mood, subject line length, and body wrapping. This Skill generates those messages automatically by analyzing diffs and enforcing best practices for clear, informative version control history.

Does this tool work with standard git version control workflows?▼

Yes, it works with standard git version control workflows by analyzing staged diffs and git status output. It requires your local repository changes to generate conventional commit messages with accurate scopes and descriptions.

What is the conventional commits specification for git changes?▼

The conventional commits specification structures git history by enforcing commit types, scopes, and descriptions. This Skill applies that standard by analyzing your code changes to generate messages with appropriate types like feat or fix, along with detailed bodies and footers.

Can I automatically add issue references to my git commit body?▼

Yes, you can automatically include issue references in your commit body. This Skill enforces best practices for footer inclusion and body content, ensuring your generated commit message references related issues alongside the descriptive changes.

Related Skills

Explore More Software Engineering Skills→
B-GalatiB-Galati
4

git-commit

Generate Conventional Commits messages from Git status and diff.

Community
Intermediate
mattg101mattg101
1

gcp-copy

Stage all changes, commit with a message, and push to a remote Git repository.

Community
Basic
dorriodorrio

ln-742-precommit-setup

Configure Husky, lint-staged, commitlint, and Python pre-commit hooks.

Community
Intermediate
dotBeepsdotBeeps

commit

Create Conventional Commits with staging, scope detection, amend, and fixup workflows.

Community
Intermediate