commit-architect

Create atomic commits from staged git changes with logical grouping.

Updated Jun 15, 2025
One-click install
npx skills add https://github.com/patrickhaahr/dotfiles --skill commit-architect
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: commit-architect
Source: https://github.com/patrickhaahr/dotfiles/tree/main/opencode/.config/opencode/skills/commit-architect
Command: npx skills add https://github.com/patrickhaahr/dotfiles --skill commit-architect

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill analyzes git changes and creates clean, atomic commits that follow project conventions, reducing noise and improving traceability.

Core Features & Use Cases

  • Automatic commit structuring: Plans splits across directories and concerns to maximize clarity.
  • Enforces separation of concerns: Keeps related changes in their own commits and pairs tests with implementations.
  • Use Case: When you modify many files across components, run this skill to generate a minimal set of coherent commits with descriptive messages.

Quick Start

Run in a repository with staged changes to produce an atomic commit plan and commit messages.

Frequently Asked Questions about commit-architect

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

FAQPage Schema
How do I split staged git changes into atomic commits?

To split staged git changes into atomic commits, this Skill analyzes multi-file changes and refactors to plan logical groupings based on separation of concerns. It then suggests split decisions to produce actionable commit messages.

What are atomic commits in version control and when do I need them?

Atomic commits in version control are single, self-contained changes that keep related modifications together and pair tests with implementations. You need them when modifying many files across components to improve traceability.

Can I automatically generate git commit messages from staged changes?

You can automatically generate git commit messages from staged changes by running this Skill in your repository. It detects your existing commit style, enforces project conventions, and suggests descriptive messages for the planned commits.

Does this tool enforce separation of concerns for multi-file git changes?

Yes, this tool enforces separation of concerns for multi-file git changes by planning splits across directories. It keeps related changes in their own commits and pairs tests with implementations to maximize clarity.

What is the best way to structure commits across multiple directories?

The best way to structure commits across multiple directories is to analyze the changes and plan logical groupings. This Skill refactors changelists to produce a minimal set of coherent commits with descriptive messages.