git-commit-guidelines
SolidEnforce 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.
Install
Quality Score: 85/100
Skill Content
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
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.
git-commits
Git Commit Rules
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.
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.
git-commits
Git Commit Rules