commit

Run the repository quality gate, stage changes, and commit with rationale-first messages.

Updated Apr 21, 2026
One-click install
npx skills add https://github.com/mliudev/agent-workflows --skill commit-mliudev
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: commit
Source: https://github.com/mliudev/agent-workflows/tree/main/skills/claude/commit
Command: npx skills add https://github.com/mliudev/agent-workflows --skill commit-mliudev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Ensures changes are committed only after the repository's quality gate passes, and the commit messages explain the rationale, not just the changed lines.

Core Features & Use Cases

  • Quality-gate guarded commits: runs the repo's gate before committing.
  • Rationale-first messages: commit notes explain why the change exists and what changed.
  • Fine-grained commits: one logical change per commit. Use cases include PR-ready commits for feature work, bug fixes, and refactor changes that require clear intent.

Quick Start

Run your repository’s quality gate, stage the intended changes, and commit with a message that explains the why, not just the what.

Frequently Asked Questions about commit

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

FAQPage Schema
How do I automate git commits to only run after code quality checks pass?

You can automate git commits after quality checks by running the repository's quality gate, staging granular changes, and generating a descriptive commit message. This ensures changes are only committed when pre-commit validation succeeds.

How do I write git commit messages that explain the rationale for code changes?

To write rationale-first git commit messages, explain why the change exists and what it changed, rather than just listing the modified lines. This approach ensures fine-grained commits with one logical change per commit.

What is the best way to manage granular staging for small features and bug fixes?

The best way to manage granular staging for small features and bug fixes is by committing one logical change at a time. This workflow ensures pre-commit checks validate each specific change before generating a meaningful commit message.

Can I use a quality gate workflow for refactoring changes on a main branch?

Yes, you can use a quality gate workflow for refactoring changes on a main branch. This conventional workflow handles small features, bug fixes, and refactors by ensuring the repository gate passes before committing the staged changes.

Why should I use an automated workflow for descriptive commits instead of committing manually?

Using an automated workflow for descriptive commits prevents committing code when the quality gate fails and enforces rationale-first notes. Manual commits often skip pre-commit checks and lack messages that justify the specific change.