skills.rest
CivicActions
CivicActionsOFFICIAL
Explore all skills by this author →
WebsiteGitHub

organize-commits

Group unstaged changes into atomic git commits using project conventions.

2|Updated May 24, 2026
Search Tags:#automation#git#workflow#version control#refactoring#commits
One-click install
npx skills add https://github.com/CivicActions/ai-runbook-jh --skill organize-commits-civicactions
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: organize-commits
Source: https://github.com/CivicActions/ai-runbook-jh/tree/main/skills/organize-commits
Command: npx skills add https://github.com/CivicActions/ai-runbook-jh --skill organize-commits-civicactions

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill solves the problem of disorganized working trees and unclear commit histories by guiding the AI to group changes into logical, atomic units that follow project-specific conventions.

Core Features & Use Cases

  • Logical Grouping: Automatically identifies natural groupings like bug fixes, features, or refactors from your unstaged changes.
  • Convention Enforcement: Integrates with project contracts to ensure commit messages and issue references strictly adhere to team standards.
  • Use Case: Use this when you have a mix of feature code, test updates, and documentation changes in your working tree and need to prepare them for a clean, professional pull request.

Quick Start

Ask the AI to organize your current changes into logical commits based on the project contract.

Frequently Asked Questions about organize-commits

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

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

To organize uncommitted git changes into logical commits, this skill analyzes your working tree and groups unstaged changes into atomic units based on natural groupings like bug fixes or features.

Can I enforce commit message conventions when staging a messy working tree?▼

You can enforce commit message conventions by applying project-specific formatting rules and issue tracker references defined in your project contract to generate standardized commit sequences.

What is the best way to split mixed feature and documentation changes for a pull request?▼

The best way to split mixed changes for a pull request is to automatically identify natural groupings within your working tree, separating feature code, test updates, and documentation into distinct atomic commits.

Do I need project-specific rules to prepare atomic git commits?▼

You need project-specific tracker and commit formatting rules defined in a project contract to ensure the generated atomic commit sequences strictly adhere to your team's standards.

Does this workflow operate on local development environments only?▼

This workflow operates on local development environments to analyze the working tree and prepare clean, logical commit sequences locally before you push them for a pull request.

Related Skills

Explore More Software Engineering Skills→
etendosoftwareetendosoftware
1

etendo-workflow-manager

Create Jira and GitHub issues with Etendo workflow conventions.

Official
Advanced
VYRE-StudiosVYRE-Studios

commit-push-pr

Commit staged changes, push the branch, and open a pull request via GitHub CLI.

Official
Intermediate
YoshikemoloYoshikemolo
5

git-jira-integration

Generate Git branch names and validate commit messages against Jira issues.

Community
Intermediate
toilahuonggtoilahuongg
10

git-cm

Commit staged or unstaged git changes with conventional commit messages.

Community
Basic