git-commit-guidelines

Generate Git commit messages combining GitMoji prefixes with Conventional Commits and Co-Authored-By for AI-assisted commits.

306|17|Updated Sep 5, 2025
One-click install
npx skills add https://github.com/PackmindHub/packmind --skill git-commit-guidelines
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: git-commit-guidelines
Source: https://github.com/PackmindHub/packmind/tree/main/.claude/skills/git-commit-guidelines
Command: npx skills add https://github.com/PackmindHub/packmind --skill git-commit-guidelines

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill enforces best-practice git commit messaging by combining GitMoji prefixes with Conventional Commits to improve clarity and traceability.

Core Features & Use Cases

  • Enforces standardized commit messages using GitMoji prefixes that map to conventional commit types.
  • Pre-commit workflow guidance to ensure user approval and quality gates before commits, preventing accidental or harmful changes.
  • AI-assisted commits support by including Co-Authored-By headers while preserving human intent and requiring explicit confirmation. Use Case: When preparing a patch for a feature, the AI suggests a compliant commit message and awaits your approval before executing the commit.

Quick Start

Start by enabling the git-commit-guidelines skill in your agent and trigger a commit with the prompt: "Prepare a compliant commit message for my current changes."

Frequently Asked Questions about git-commit-guidelines

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

FAQPage Schema
How do I enforce standardized commit messages in Git?

Standardized commit messages use GitMoji prefixes combined with Conventional Commits to categorize changes and improve clarity. This Skill enforces that pattern automatically, requiring your approval before finalizing each commit to prevent accidental or harmful changes.

What's the best way to structure Git commits for code quality and traceability?

Combine GitMoji emoji prefixes with Conventional Commits format—mapping emoji to commit types like feature, fix, or docs. This approach improves clarity across development workflows and makes commit history scannable and traceable.

How do I use AI-assisted commits while maintaining code quality?

AI-assisted commits include Co-Authored-By headers to credit the AI and require your explicit approval before execution. This preserves human intent and control while leveraging AI suggestions for compliant commit messages.

Can I automate commit message generation without skipping quality checks?

Yes. This Skill generates compliant commit messages using GitMoji and Conventional Commits, then pauses for your review and approval before committing, ensuring quality gates remain in place.

What prevents dangerous or automatic commits in this workflow?

The Skill requires explicit user approval before any commit executes. It avoids dangerous automatic fixes and ensures human judgment gates every change, whether manually authored or AI-suggested.

Does this work with both manual and automated commits?

Yes. The Skill applies commit guidelines to both manual commits you write and AI-assisted commits it generates, enforcing GitMoji and Conventional Commits standards across your entire development workflow.