git-commit-guidelines

Solid

Enforce git commit best practices using gitmoji + Conventional Commits format. TRIGGER when creating commits. Prevents issue auto-closing (no Close/Fix keywords), includes Co-Authored-By for AI commits, and requires user approval before committing.

Code & Development 287 stars 14 forks Updated today Apache-2.0

Install

View on GitHub

Quality Score: 85/100

Stars 20%
82
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# Git Commit Guidelines This skill enforces git commit best practices for the Packmind project, combining gitmoji for visual commit type identification with Conventional Commits format. ## TRIGGER CHECKLIST - Read This First **TRIGGER THIS SKILL WHEN:** - [ ] User asks you to commit changes - [ ] User asks you to create a commit - [ ] You are about to run `git commit` - [ ] User says "commit this" or similar **TRIGGER IMMEDIATELY** - before running any git commit command. ## Failure Examples - What NOT To Do ### Failure 1: Committing Without User Permission ``` User: "Fix the bug in the login function" AI: [Fixes the bug] AI: [Runs git commit directly without asking] ❌ CORRECT BEHAVIOR: AI: [Fixes the bug] AI: [Asks user: "Ready to commit. Here's the proposed message: ..."] AI: [Waits for user approval] AI: [Then commits] ``` ### Failure 2: Using Close/Fix Before Issue References ``` AI: git commit -m "Fix login bug Closes #123" ❌ CORRECT BEHAVIOR: AI: git commit -m "Fix login bug #123" ✓ ``` ### Failure 3: Missing Gitmoji ``` AI: git commit -m "feat(auth): add login validation" ❌ CORRECT BEHAVIOR: AI: git commit -m "✨ feat(auth): add login validation" ✓ ``` ## Commit Message Format ``` <gitmoji> <type>(<scope>): <subject> <body> <issue-reference> Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com> ``` ### Format Rules | Element | Rule | | --...

Details

Author
PackmindHub
Repository
PackmindHub/packmind
Created
8 months ago
Last Updated
today
Language
TypeScript
License
Apache-2.0

Integrates with

Similar Skills

Semantically similar based on skill content — not just same category

Code & Development Listed

gitmoji-commit

Plan and draft git commits in the Gitmoji + Conventional Commits style — a leading emoji (✨, 🐛, ♻️ …) plus a conventional type, like "✨ feat: add avatar upload". Splits a working tree into a clean sequence of reviewable, logically-grouped commits, isolates lockfiles into their own final commit, and hands back signed, copy-paste git commands. Use whenever the user wants help committing changes, writing/improving a commit message, asks "how should I commit this", wants to break work into reviewable commits, or mentions gitmoji/git-emoji/emoji commits. The user runs git themselves — this skill produces messages and commands, it does not commit.

0 Updated 2 days ago
colachg
Code & Development Listed

git-commits

Git Commit Rules

3,795 Updated 4 months ago
parcadei
Code & Development Listed

git-commit

Create proper git commits from repository changes using Conventional Commits headers and a high-signal commit body that explains why the change was needed and what was done. Use when the user says commit this, make a commit, create a commit, draft a commit message from current changes, or asks for a proper git commit.

6 Updated 1 weeks ago
mgajewskik
Code & Development Listed

cli-git-conventional

Enforce Conventional Commits v1.0.0, SemVer 2.0.0, branch naming, and human ghostwriter style on all git/jj operations. Zero AI markers. Use on 'commit', 'branch', 'tag', 'release', 'changelog', 'semver', 'bump version', 'next version', 'CHANGELOG.md'. Also trigger proactively when the user shares code changes without mentioning commit.

4 Updated yesterday
Destynova2
Code & Development Solid

git-commits

Git Commit Rules

496 Updated 1 months ago
vibeeval