committing-code

Group and stage file changes into atomic commits with conventional messages.

35|5|Updated Jul 5, 2025

Search Tags:#automation #git #workflow #commit #code-review #atomic

Ready to run

npx skills add https://github.com/alexei-led/cc-thingz --skill committing-code-alexei-led

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: committing-code
Source: https://github.com/alexei-led/cc-thingz/tree/main/plugins/dev-workflow/skills-codex/committing-code
Command: npx skills add https://github.com/alexei-led/cc-thingz --skill committing-code-alexei-led

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Group related changes into atomic, well-scoped commits to improve history clarity and code reviews.

Core Features & Use Cases

Auto-grouping changes by feature, bug fix, docs, or refactor
Propose conventional-commit style messages based on analyzed diffs
Reinforce safety by excluding sensitive files from automatic staging

Quick Start

Describe the changes you want to commit and let the tool group them into atomic commits with contextual messages.

Frequently Asked Questions about committing-code

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

FAQPage Schema

How do I group multiple file changes into atomic git commits automatically?▼

This tool automates grouping changes into atomic git commits by analyzing your current diffs and proposing logical commit blocks. It categorizes changes by feature, bug fix, docs, or refactor to keep your history clean and well-scoped.

What is the best way to write conventional commit messages for multiple staged changes?▼

Writing conventional commit messages for multiple changes is handled by analyzing your diffs to propose contextual messages. The tool groups related files into atomic commits and generates appropriate conventional-commit style messages for each block.

Can I automatically split a large working directory change into separate logical commits?▼

You can split a large change into separate logical commits as the tool analyzes your session's edits and proposes commit blocks. It groups related changes together to ensure each atomic commit represents a single logical modification.

Does this workflow exclude sensitive files from automatic git staging?▼

The workflow excludes sensitive files from automatic git staging by enforcing safe execution with prompts and guards. This ensures sensitive files are not automatically staged, protecting your repository from accidental exposure.

How do I prepare my edited files for code review with clean history?▼

Preparing files for code review with clean history involves describing your changes and letting the tool group them into atomic commits. This creates a logical history where each commit represents a distinct unit of work, making reviews easier.