commit

Enforce atomic conventional Git commits with pre-commit validation and user review.

1|Updated Jan 31, 2026

Search Tags:#git #code review #commit #conventional commits #pre-commit #atomic commits

Ready to run

npx skills add https://github.com/jugrajsingh/skillgarden --skill commit-jugrajsingh

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: commit
Source: https://github.com/jugrajsingh/skillgarden/tree/main/plugins/gitmastery/skills/commit
Command: npx skills add https://github.com/jugrajsingh/skillgarden --skill commit-jugrajsingh

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the enforcement of atomic, conventionally formatted Git commits, preventing common errors and ensuring code quality through strict hooks and user-reviewed steps.

Core Features & Use Cases

Atomic Commits: Guides the user to create small, logical commits, one at a time.
Conventional Commits: Enforces the <type>(<scope>): <subject> format for commit messages.
Hook Enforcement: Integrates with pre-commit to validate staged files before committing.
User Review: Presents each commit for explicit user approval before execution.
Submodule Handling: Provides a safe workflow for committing changes within Git submodules.

Quick Start

Use the commit skill to create an atomic commit for the changes in src/auth.py and src/tokens.py with the message "feat(auth): add JWT refresh endpoint".

Frequently Asked Questions about commit

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

FAQPage Schema

How do I enforce conventional commits format in my Git workflow?▼

Enforcing conventional commits format in Git requires validating staged files against the `<type>(<scope>): <subject>` pattern. This Skill guides you through a user-reviewed workflow to ensure commit messages adhere to this standard before execution.

What are atomic commits and how do I create them in Git?▼

Atomic commits are small, logical changes grouped one at a time. You can create them by using a guided workflow that reviews staged files, prevents anti-patterns like chained commands, and requires explicit user approval before executing the commit.

Does pre-commit work with conventional commit validation?▼

Pre-commit works with conventional commit validation by running hooks to validate staged files before committing. This integration ensures code quality by preventing anti-patterns like wildcards and AI footers during the commit process.

How do I handle Git submodules when making atomic commits?▼

Handling Git submodules during atomic commits requires a safe workflow that recognizes submodule updates. This Skill provides a specific workflow to properly stage and commit changes within Git submodules while maintaining atomic commit standards.

Why should I prevent wildcards and AI footers in Git commit messages?▼

Preventing wildcards and AI footers in Git commit messages ensures clean, readable history and avoids automated noise. This Skill blocks these anti-patterns during the user-reviewed commit workflow to maintain strict commit hygiene.

Can I review a Git commit before it is executed?▼

Reviewing a Git commit before execution is possible through a user-approved workflow. This Skill presents each generated commit summary for explicit approval, ensuring you maintain control over the conventional commit message and staged files before finalizing.