g

Organizes uncommitted changes into logical commits and pushes them to the Git repository.

2|Updated Mar 12, 2026
One-click install
npx skills add https://github.com/ipswitch8/CC_tools --skill g-ipswitch8
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: g
Source: https://github.com/ipswitch8/CC_tools/tree/main/skills/g
Command: npx skills add https://github.com/ipswitch8/CC_tools --skill g-ipswitch8

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Review all uncommitted changes, organize related edits into logical commits, and push to the Git repo, reducing messy history and the risk of mistakes.

Core Features & Use Cases

  • Review git status to see uncommitted changes.
  • Group related changes into cohesive commits.
  • Push commits to the remote repository with safeguards against accidental data loss.

Quick Start

Review your working directory and generate a clean commit plan, then push to the repository.

Frequently Asked Questions about g

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

FAQPage Schema
How do I organize multiple uncommitted changes into logical git commits?

To organize uncommitted changes into logical git commits, review your working directory status to group related edits into cohesive, self-contained scopes ready for review and push.

How do I group staged and untracked files into cohesive commits for code review?

Grouping staged and untracked files into cohesive commits requires inferring change scopes from related edits. The skill applies change-detection accuracy to separate mixed changes into self-contained commits with descriptive messages.

What's the best way to ensure safe push to remote without accidental data loss?

The best way to ensure a safe push to remote is to enforce safeguards against accidental data loss during the push process. This skill applies safe push-to-remote safeguards after organizing your commits.

How do I generate descriptive commit messages from mixed changes in version control?

To generate descriptive commit messages from mixed changes, infer the logical scope of related edits. This skill enforces cohesive commit scope inference and descriptive commit messages for version-control safety checks.

Why should I organize related edits into self-contained commits before pushing?

You should organize related edits into self-contained commits to reduce messy history and the risk of mistakes. This approach ensures change-detection accuracy and clean commit scope inference before a safe push-to-remote.