commit

Enforce atomic Git commits with strict verb, scope, and message formatting.

Updated Jan 4, 2026
One-click install
npx skills add https://github.com/Kasuletrevor/marconi-elearn --skill commit-kasuletrevor
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: commit
Source: https://github.com/Kasuletrevor/marconi-elearn/tree/main/.gemini/skills/commit
Command: npx skills add https://github.com/Kasuletrevor/marconi-elearn --skill commit-kasuletrevor

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill enforces a strict, disciplined approach to Git commits, ensuring each commit is atomic, well-described, and contributes to a clean, understandable project history.

Core Features & Use Cases

  • Atomic Commits: Enforces the "one commit, one file" rule by default, promoting focused changes.
  • Structured Commit Messages: Mandates a clear format (verb(scope): message) for commit messages, improving readability and discoverability.
  • Controlled Vocabulary: Restricts commit verbs to a predefined, semantic set (refactor, fix, feat, etc.) to convey intent accurately.
  • Use Case: When refactoring a large module, use this Skill to commit each file's changes individually with precise refactor messages, making it easy to review and revert specific parts if needed.

Quick Start

Use the commit skill to stage and commit the file backend/src/models/user.py with the message feat(user): add profile picture field.

Frequently Asked Questions about commit

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

FAQPage Schema
How do I enforce atomic git commits for individual file changes?

Enforcing atomic git commits involves staging and committing changes file by file. This approach ensures focused modifications, clear intent signaling, and a highly review-friendly project history.

What is the proper format for structured git commit messages?

The proper format for structured git commit messages is verb(scope): message. This mandates using a controlled vocabulary of verbs like feat, fix, or refactor to convey intent accurately and improve readability.

How do I commit refactoring changes file by file?

To commit refactoring changes file by file, stage each modified file individually and apply a structured commit message using the refactor verb. This creates atomic commits with precise intent signaling for easy review.

Why use a controlled vocabulary for git commit verbs?

Using a controlled vocabulary for git commit verbs restricts changes to a predefined semantic set like feat, fix, or refactor. This standardizes developer workflow intent, improving commit history discoverability and readability.

Does strict file-by-file committing work for large module refactoring?

Strict file-by-file committing works for large module refactoring by breaking down modifications into atomic, single-file commits. This allows precise tracking and easy reversion of specific parts without affecting the entire module.