skills.rest
mituso89
mituso89COMMUNITY
Explore all skills by this author →
GitHub

m-git-commit

Guide Git commit message creation with conventional commit standards.

2|Updated Jul 2, 2026
Search Tags:#code quality#git#conventional commits#commit messages#developer productivity
One-click install
npx skills add https://github.com/mituso89/Spec-Driven-Development-toolkits --skill m-git-commit
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: m-git-commit
Source: https://github.com/mituso89/Spec-Driven-Development-toolkits/tree/main/m-git-commit
Command: npx skills add https://github.com/mituso89/Spec-Driven-Development-toolkits --skill m-git-commit

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill addresses the challenge of creating Git commit messages that adhere to conventional commit guidelines, reducing the likelihood of commit message errors and enhancing code readability.

Core Features & Use Cases

  • Conventional Commit Formatting: Guides the user in crafting commit messages that are easy to read and maintain.
  • Automated Verification: Checks the commit message against a commit-msg hook to ensure it meets the project's standards.
  • Fixup and Squash: Provides commands to fold corrections into earlier commits or combine multiple commits into one.

Quick Start

Run m-git-commit to start drafting your Git commit message.

Frequently Asked Questions about m-git-commit

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

FAQPage Schema
How do I format Git commit messages using conventional commit guidelines?▼

Conventional commit messages require a specific type, scope, subject, and body structure. This Skill guides you through drafting each component to ensure your Git commits meet standard formatting guidelines and improve code readability.

Can I use a commit-msg hook to validate conventional commit formatting?▼

Yes, automated verification checks your commit message against a commit-msg hook. This validation ensures the submitted Git commit meets your project's conventional commit standards before it is finalized.

What is the best way to manage commit history with fixup and squash operations?▼

Fixup and squash operations fold corrections into earlier commits or combine multiple commits into one. This approach streamlines your Git commit history management by consolidating redundant entries.

How do I create a conventional commit message step by step?▼

Run the initialization command to start the interactive process. The system prompts you to select a commit type, define the scope, write a concise subject, and format the body according to conventional commit rules.

Does this tool support both fixup and squash for Git commit history management?▼

Yes, the tool supports both fixup and squash commands. These features allow you to fold corrections into earlier commits or combine multiple commits into a single, clean Git history entry.

Related Skills

Explore More Software Engineering Skills→
borkwebborkweb
7

commit-writer

Generate conventional git commit messages from staged diffs and repository history.

Community
Intermediate
MelvynxMelvynx
223

commit

Generate conventional commit messages and push changes to the repository.

Community
Basic
mostafa-ismail-2004mostafa-ismail-2004

git-workflow

Guide Git branching, commit, merge, and release decisions for collaborative development.

Community
Advanced
ccfccf

changelog-automation

Generate CHANGELOG.md from commits, PRs, and releases using Keep a Changelog.

Community
Advanced