One-click install
npx skills add https://github.com/corticalstack/claude-code-flow --skill commit-corticalstack
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: commit
Source: https://github.com/corticalstack/claude-code-flow/tree/main/.claude/skills/commit
Command: npx skills add https://github.com/corticalstack/claude-code-flow --skill commit-corticalstack

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps you stage and create accurate git commits after reviewing changes, preventing messy, wrongly grouped, or incorrectly attributed commits.

Core Features & Use Cases

  • Commit planning and grouping: Reviews git status and git diff to decide how many commits to make and which files belong together.
  • User confirmation before execution: Presents the exact files to add and the commit message(s) to approve before running any git commands.
  • Commit hygiene safeguards: Enforces explicit-only usage, avoids adding co-author or AI attribution, and writes messages in imperative mood as if you authored them.

Quick Start

Ask to commit your changes by saying: "Create the commit(s) for the changes in this session."

Frequently Asked Questions about commit

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

FAQPage Schema
How do I create logical git commits from a messy working tree?

This skill stages and creates logical git commits by reading git status and git diff to group related changes, proposing an atomic commit plan for your approval before executing any git commands.

Can I review the commit message and staged files before the git commit is created?

Yes, you can review the git commit plan. The skill presents the exact files to add and the proposed imperative commit messages, requiring your explicit confirmation before running any git commands.

How do I ensure my git commit messages have no AI attribution or co-author tags?

To ensure git commit messages have no AI attribution, this skill enforces commit hygiene safeguards by writing messages in the imperative mood as if you authored them, avoiding any co-author tags.

Does this git commit tool use git add -A to stage all repository changes automatically?

No, this git commit tool does not use git add -A. It enforces repository hygiene by using specific file adds based on the reviewed git diff, requiring explicit invocation only to stage changes.

What's the best way to group multiple file changes into separate atomic commits?

The best way to group file changes into atomic commits is using a commit planning workflow that analyzes your git diff, groups related modifications, and stages each set separately with a distinct imperative commit message.