commit

Plan and execute git commits with user approval on non-main branches.

2|Updated Feb 9, 2026

Search Tags:#git #workflow #planning #commit #atomic-commits #version-control #commit-message

Ready to run

npx skills add https://github.com/SiTaggart/.agents --skill commit-sitaggart

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: commit
Source: https://github.com/SiTaggart/.agents/tree/main/skills/commit
Command: npx skills add https://github.com/SiTaggart/.agents --skill commit-sitaggart

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Git commits often lack planning and consistency, leading to messy histories and unclear justification for changes.

Core Features & Use Cases

Plan multi-file commits by grouping related changes into a single, logical unit.
Draft and enforce descriptive commit messages in imperative mood, with optional checks before applying.
Execute commits only after explicit user confirmation, preserving attribution to you (no Claude authorship).

Quick Start

Review changes, plan commits with descriptive messages, and confirm to execute them.

Frequently Asked Questions about commit

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

FAQPage Schema

How do I plan atomic git commits across multiple files?▼

To plan atomic git commits across multiple files, you group related changes into a single logical unit and generate a structured commit plan. This Skill validates commit messages in imperative mood before executing them on non-main branches after user confirmation.

What are atomic commits and when do I need them?▼

Atomic commits are cohesive, single-purpose commits that group related changes across multiple files into one logical unit. You need them during active development when changes span multiple files and require a clear, clean version-control history.

How do I enforce imperative mood in git commit messages?▼

To enforce imperative mood in git commit messages, this Skill validates drafted messages to ensure they follow the imperative convention. It generates structured commit plans and checks message formatting before applying them.

Can I review git commits before they are executed?▼

Yes, you can review commits before execution because this Skill generates a structured plan and requires explicit user confirmation. It only executes commits on non-main branches after you approve the drafted plan and message.

Does this Skill work on main branches?▼

No, this Skill does not work on main branches because it enforces safety rules by executing commits only on non-main branches. This constraint prevents accidental direct commits to protected version-control workflows.