commit

Creates staged git commits with planned messages after user confirmation.

1|1|Updated Feb 2, 2026
One-click install
npx skills add https://github.com/corticalstack/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/flow/tree/main/.claude/skills/commit
Command: npx skills add https://github.com/corticalstack/flow --skill commit-corticalstack

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? It turns uncommitted session changes into clean, well-organized git commits without the user manually reviewing diffs, grouping files, and writing messages. ## Core Features & Use Cases - Change Analysis: Runs git status and git diff to understand modifications, even when conversation context was cleared during long sessions. - Commit Planning: Groups related files into logical atomic commits and drafts imperative-mood messages focused on why changes were made. - Confirmation Gate: Presents the full commit plan and waits for explicit approval before staging specific files and committing. - Use Case: After a long coding session with mixed changes, invoke /commit to get a proposed split into focused commits, approve the plan, and have them created without AI attribution or co-author lines. ## Quick Start Ask the assistant to commit the current session's changes and it will propose a commit plan for your approval.

Frequently Asked Questions about commit

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

FAQPage Schema
How do I commit changes made during an AI coding session?▼

Invoke the commit command explicitly and the assistant reviews git status and git diff, proposes one or more logical commits with messages, and creates them after you confirm the plan.

How to split mixed changes into multiple git commits?▼

The skill groups related files by analyzing the diff and drafts separate commits for each logical change set. It stages files individually with git add rather than using -A, keeping each commit focused and atomic.

Does this add Claude or AI attribution to commit messages?▼

No. The skill explicitly forbids co-author lines, Generated-with-Claude messages, and any AI attribution. Commits are authored solely by the user as if they wrote the messages themselves.

Can it run automatically without being asked?▼

No. The skill is explicit-only with model invocation disabled, so it runs only when the user invokes /commit or directly asks to commit, never autonomously.

What happens if conversation context was cleared before committing?▼

The skill relies on git status and git diff rather than conversation history to understand changes. If intent is unclear, it reads the modified files or asks the user before proposing commits.