commit-work

Automate git commit creation with patch staging and Conventional Commits enforcement.

1|1|Updated Apr 19, 2026

Search Tags:#git #workflow #commit #staging #review #conventional-commits #split-commits

Ready to run

npx skills add https://github.com/RamonsDka/the-architect-overlay --skill commit-work-ramonsdka

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: commit-work
Source: https://github.com/RamonsDka/the-architect-overlay/tree/main/skills/commit-work
Command: npx skills add https://github.com/RamonsDka/the-architect-overlay --skill commit-work-ramonsdka

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Streamlines the process of creating clean, reviewable git commits by guiding you to inspect changes, split work into logical units, and enforce Conventional Commits formatting.

Core Features & Use Cases

Smart commit boundaries: automatically suggest logical splits across features, fixes, refactors, tests, and dependencies.
Patch staging: enable fine-grained, hunk-by-hunk staging to keep commits focused.
Conventional Commits enforcement: ensure type and scope correctness in every commit message.
Review-ready deliverables: provide final commit messages and staging commands for efficient reviews.

Quick Start

Describe your changes and ask the skill to split them into logical commits and generate Conventional Commits messages.

Frequently Asked Questions about commit-work

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

FAQPage Schema

How do I split unstaged git changes into logical conventional commits?▼

To split unstaged git changes into logical conventional commits, inspect the working tree and use patch staging to stage hunks selectively. This process groups related modifications into focused commits, generating descriptive messages that adhere to the Conventional Commits format for review-ready deliverables.

How does patch staging help create review-ready git commits?▼

Patch staging enables fine-grained, hunk-by-hunk staging of code changes to keep commits focused and review-ready. By selectively staging specific segments rather than entire files, it separates feature additions, fixes, and refactors into isolated, safe-to-merge conventional commits.

What is the conventional commits format for structuring git commit messages?▼

The conventional commits format structures git commit messages by enforcing type and scope correctness in every commit. This discipline categorizes changes into types like features, fixes, or refactors, ensuring well-structured messages that are easy to review and safe to merge.

Can I automatically generate commit boundaries for mixed code changes?▼

Yes, you can automatically generate commit boundaries for mixed code changes. The workflow analyzes the working tree and suggests logical splits across features, fixes, refactors, tests, and dependencies, providing final commit messages and staging commands for efficient reviews.

Do I need any external git tools or dependencies to enforce split commits?▼

No external git tools or dependencies are required to enforce split commits. The workflow operates independently to inspect the working tree, suggest logical commit boundaries, perform patch staging, and generate conventional commit messages without additional package dependencies.