flow-commit

Automate commit planning and grouping into atomic Conventional Commits.

3|Updated Oct 5, 2025
One-click install
npx skills add https://github.com/korchasa/flow --skill flow-commit
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: flow-commit
Source: https://github.com/korchasa/flow/tree/main/framework/skills/flow-commit
Command: npx skills add https://github.com/korchasa/flow --skill flow-commit

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates commit planning and grouping to enforce atomic commits and consistent messaging across a codebase.

Core Features & Use Cases

  • Automated merge of related changes into a single, atomic commit following Conventional Commits.
  • Documentation alignment: ensures documentation updates reflect code changes.
  • Compliance: guarantees mandatory commit message formats, and provides an automated planning flow to minimize risky splits.

Quick Start

Run the flow-commit workflow to initialize a plan, audit changes, and apply atomic commits automatically.

Frequently Asked Questions about flow-commit

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

FAQPage Schema
How do I automate atomic commits with conventional commit messages?

Automating atomic commits requires grouping related changes to enforce standardized conventional commit messages. This workflow audits codebase modifications and applies safe grouping to merge related updates into a single commit automatically.

What is the best way to keep documentation synchronized with code changes during automated commits?

Keeping documentation synchronized during automated commits involves aligning documentation updates directly with code changes. The automated planning flow ensures documentation reflects the codebase modifications before applying the final atomic commit.

How does automated commit grouping minimize risky splits in a software project?

Automated commit grouping minimizes risky splits by auditing changes and merging related modifications across files into a single atomic commit. This planning flow ensures cross-file consistency and robust error handling throughout the workflow.

Can I enforce mandatory commit message formats automatically across my codebase?

Enforcing mandatory commit message formats automatically across a codebase guarantees compliance with conventional commits. The automated workflow plans and groups changes to consistently apply the required standardized messaging.

Do I need specific dependencies to run an automated conventional commits workflow?

Running an automated conventional commits workflow requires no specific external dependencies. The workflow independently initializes a plan, audits changes, and applies atomic commits within your software project.

When should I use an automated atomic commit workflow instead of manual git commits?

Use an automated atomic commit workflow when a software project requires end-to-end commit hygiene, documentation synchronization, and cross-file consistency. It provides robust error handling and standardized messaging that manual commits often lack.