skills.rest
WarLikeLaux
WarLikeLauxCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

commit

Create atomic Git commits with enforced message formatting and pre-commit checks.

10|6|Updated Dec 2, 2025
Search Tags:#git#code review#version control#commit#developer workflow#atomic commits
One-click install
npx skills add https://github.com/WarLikeLaux/yii2-book-catalog --skill commit-warlikelaux
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: commit
Source: https://github.com/WarLikeLaux/yii2-book-catalog/tree/main/.claude/skills/commit
Command: npx skills add https://github.com/WarLikeLaux/yii2-book-catalog --skill commit-warlikelaux

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill enforces a structured and atomic Git commit process, ensuring a clean, understandable, and maintainable project history.

Core Features & Use Cases

  • Atomic Commits: Guides the creation of small, focused commits for individual changes.
  • Strict Formatting: Enforces a specific commit message format including task IDs and precise verb usage.
  • Pre-commit Checks: Integrates with project build (make dev) to ensure code quality before committing.
  • Use Case: When you've made several unrelated changes (e.g., fixed a bug, added a small feature, updated documentation), this Skill helps you create separate, well-described commits for each, rather than one large, messy commit.

Quick Start

Use the commit skill to create a new git commit for the staged changes.

Frequently Asked Questions about commit

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

FAQPage Schema
How do I create atomic git commits for multiple unrelated changes?▼

Atomic git commits separate unrelated changes into focused commits. This Skill guides you through staging individual changes, analyzing diffs, and generating specific commit messages to maintain a clean project history.

What is the best way to enforce a strict git commit message format with task IDs?▼

Enforcing a strict git commit message format requires specific past-tense verbs and task IDs. This Skill automatically generates compliant commit messages by analyzing staged diffs and applying project-specific formatting rules.

How do I analyze staged and unstaged git diffs before committing?▼

Analyzing staged and unstaged git diffs is handled by running make d and make dc commands. This Skill integrates these diff checks into the workflow to review changes before generating your atomic commit.

Can I run pre-commit checks and build verification during the git commit process?▼

Pre-commit checks and build verification integrate directly into the git commit process via make dev. This Skill enforces code quality checks before allowing changes to be staged and committed to the repository.

Why should I use atomic commits instead of committing all changes at once?▼

Atomic commits isolate individual changes like bug fixes or documentation updates into separate commits. This approach creates an understandable and maintainable project history rather than one large, messy commit.

Related Skills

Explore More Software Engineering Skills→
andeartandeart
1

suggest-commit

Generate a git commit message from the current diff.

Community
Intermediate
bswrundquistbswrundquist

commit-and-push

Commit staged changes using conventional commits and push them to the remote repository.

Community
Basic
cartridge-ggcartridge-gg
80

pre-commit-check

Run Husky pre-commit hooks for format, lint, and test checks.

Official
Intermediate
paulnsorensenpaulnsorensen
2

commit

Stage specific files and create conventional commits in Git.

Community
Intermediate