gc

Group uncommitted changes into atomic conventional git commits and push them.

Updated Mar 23, 2026

Search Tags:#git #workflow #commits #version-control #conventional-commits

Ready to run

npx skills add https://github.com/mia-cx/.agents --skill gc-mia-cx

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: gc
Source: https://github.com/mia-cx/.agents/tree/main/skills/gc
Command: npx skills add https://github.com/mia-cx/.agents --skill gc-mia-cx

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Splits uncommitted changes into a small set of logical, single-concern git commits, then executes the commits and pushes to remote. Use when the user wants to organize changes into logical commits, split a large change into multiple commits, or create a series of conventional commits from the current working tree.

Core Features & Use Cases

Organize changes by concern (config, code, tests, docs) into atomic commits.
Automatically execute each commit and push to the remote, preserving history readability.
Supports a workflow that guides inspection, grouping, and conventional-commit messaging.

Quick Start

Execute the current worktree into a series of atomic commits and push them to the remote with a single activation.

Frequently Asked Questions about gc

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

FAQPage Schema

How do I split uncommitted git changes into multiple logical commits?▼

Grouping uncommitted changes into atomic commits organizes a messy worktree by inspecting the git state, grouping files by concern like config or tests, and generating single-concern conventional commit messages for a readable history.

How do I organize a large set of staged changes into conventional commits?▼

You can organize large changes into conventional commits by grouping modified files into logical categories such as docs, config, or code, then applying a deterministic workflow that generates conventional messages and pushes commits.

What is the best way to create atomic git commits from a messy working tree?▼

The best way to create atomic commits from a messy working tree is using a deterministic workflow that inspects uncommitted changes, groups them by concern, and generates conventional commit messages to preserve history readability.

Does this conventional commit workflow automatically push git commits to the remote?▼

Yes, the workflow automatically pushes the resulting atomic commits to the remote after inspecting the git state, grouping changes by concern, and generating conventional commit messages to ensure a clean history.

When should I split changes into single-concern git commits?▼

Split changes into single-concern git commits when organizing large changes across config, code, tests, or docs, ensuring a clean, readable version-control history through multiple conventional commits rather than one mixed commit.