flow-commit

Automate FLOW commit processes with diff validation and structured messages.

25|3|Updated Feb 19, 2026
One-click install
npx skills add https://github.com/benkruger/flow --skill flow-commit-benkruger
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: flow-commit
Source: https://github.com/benkruger/flow/tree/main/skills/flow-commit
Command: npx skills add https://github.com/benkruger/flow --skill flow-commit-benkruger

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill standardizes and secures the commit process within FLOW by guiding users to review diffs, stage changes, and produce structured commit messages aligned with per-branch state and workflow requirements.

Core Features & Use Cases

  • Diff review and staging guidance: Helps ensure every change is examined before it's committed, reducing accidental changes.
  • Commit message generation: Creates descriptive, structured messages that reflect the change set and WHY it matters.
  • Flow integration: Works across multi-branch worktrees and FLOW phases (plan, code, review, learn) to keep history clean and auditable.

Quick Start

Run /flow:flow-commit to prepare and commit changes for the current FLOW feature.

Frequently Asked Questions about flow-commit

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

FAQPage Schema
How do I automate git commits with structured messages across multiple worktrees?

Automated git commits across multiple worktrees require validating diffs, staging changes, and generating structured messages aligned with per-branch state to ensure idempotent, auditable commits throughout the workflow lifecycle.

What is the best way to standardize commit messages during a multi-branch workflow?

Standardizing commit messages during a multi-branch workflow requires enforcing a consistent commit structure, either full or title-only, that reflects the change set and aligns with the current branch state file.

How does per-branch state management ensure deterministic commits at workflow checkpoints?

Per-branch state management ensures deterministic commits by leveraging a state file to track workflow phases, guiding diff review, staging, and commit message generation to produce idempotent results at every checkpoint.

Can I use automated commit generation with multi-branch worktrees in version control?

Automated commit generation operates across single or multiple worktrees and branches by validating diffs and staging changes before producing structured commit messages that keep version control history clean and auditable.

Why do I need diff review before staging changes for an automated commit?

Diff review before staging changes for an automated commit helps examine every modification, reducing accidental changes and ensuring the generated commit message accurately reflects the change set and why it matters.

Does flow-commit work without external dependencies for version control automation?

Flow-commit works without external dependencies, relying solely on per-branch state management to validate diffs, stage changes, and produce structured commit messages across workflow phases like plan, code, review, and learn.