commit-split-workflow

Split diffs into commits following repository commit-message conventions.

2|Updated Jan 31, 2026

Search Tags:#automation #git #workflow #code-review #version-control #diff-analysis #commit-splitting

Ready to run

npx skills add https://github.com/MRiabov/Problemologist-AI --skill commit-split-workflow

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: commit-split-workflow
Source: https://github.com/MRiabov/Problemologist-AI/tree/main/.agents/skills/commit-split-workflow
Command: npx skills add https://github.com/MRiabov/Problemologist-AI --skill commit-split-workflow

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manual trigger only. Use this skill only when the user explicitly asks for $commit-split-workflow (or clearly requests this exact workflow) to split changes into meaningful commits with the repository's commit-message conventions. Never ask the user how to split files; read the repo instructions and infer commit boundaries from the diff.

Core Features & Use Cases

Manual trigger only: the skill does not auto-run; it derives commit groups from the diff and repo guidelines.
Precise history: produces commits with descriptive messages aligned to conventions, enabling easier reviews, rollbacks, and traceability.
Guardrails: reads repository instructions to determine grouping, handles nested repositories, and ensures changes are staged logically.

Quick Start

Trigger this workflow only when explicitly requested to split changes into meaningful commits, and let it derive commit groups from the diff and repository guidance.

Frequently Asked Questions about commit-split-workflow

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

FAQPage Schema

How do I split a large multi-file diff into meaningful commits?▼

To split a large multi-file diff into meaningful commits, this workflow reads repository conventions and infers logical boundaries directly from the changes. It batches modifications automatically without prompting the user for input on how to group files.

Can I automate splitting git changes for code review without manual intervention?▼

Yes, you can automate splitting git changes for code review by manually triggering this workflow. It automatically derives commit groups from the diff and repository guidance, ensuring changes are staged logically to enable easier reviews and rollbacks.

Does this commit-splitting workflow follow existing repository commit-message conventions?▼

Yes, this commit-splitting workflow follows repository commit-message conventions. It reads your repository instructions to determine grouping and generates descriptive messages aligned to those specific conventions for precise version-control history.

What is the best way to group nested repository changes into separate commits?▼

The best way to group nested repository changes into separate commits is using a diff-analysis workflow that enforces guardrails. It reads repository instructions, handles nested repositories, and ensures changes are staged logically without asking the user how to split files.

When should I avoid using an automated workflow to split changes?▼

You should avoid using an automated workflow to split changes unless you explicitly request it. This skill is manual trigger only and does not auto-run; it should only be activated when you clearly want to split changes into meaningful commits.