source-command-commit

Name: source-command-commit
Availability: InStock
Author: redblacktree

Creates git commits with user approval and no AI attribution.

1|1|Updated Feb 3, 2026

Search Tags:#git #code review #version control #commit #staging #commit message

Ready to run

npx skills add https://github.com/redblacktree/fastflow --skill source-command-commit-redblacktree

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: source-command-commit
Source: https://github.com/redblacktree/fastflow/tree/main/.agents/skills/source-command-commit
Command: npx skills add https://github.com/redblacktree/fastflow --skill source-command-commit-redblacktree

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? It turns the changes made during a coding session into clean, well-organized git commits without requiring the user to manually review diffs, group files, and write commit messages from scratch. ## Core Features & Use Cases - Session-Aware Commit Planning: Reviews conversation history, `git status`, and `git diff` to decide whether changes should be one commit or multiple logical commits. - Approval-Gated Execution: Presents the planned files and commit messages to the user and only commits after explicit confirmation. - Clean Attribution: Writes commit messages in imperative mood as if authored by the user, with no co-author lines or AI attribution. - Use Case: After a long refactoring session, ask the agent to commit the work; it groups related files into atomic commits, proposes messages, and executes them once you approve. ## Quick Start Ask the agent to commit the changes from this session and approve the proposed commit plan when it is presented.

Frequently Asked Questions about source-command-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?▼

Ask the agent to commit the session's changes. It reviews git status and git diff, groups related files into logical commits, proposes messages, and executes them only after you confirm the plan.

How to split uncommitted changes into multiple git commits?▼

The skill analyzes which files belong together based on the work performed, then stages specific files per commit using git add with explicit paths. It never uses git add -A or git add . to avoid mixing unrelated changes.

Does this skill add Co-Authored-By or AI attribution to commits?▼

No. The skill explicitly forbids co-author lines, Codex attribution, and generated-with messages. Commits are authored solely by the user with messages written as if the user wrote them.

Can I review the commit plan before anything is committed?▼

Yes. The skill always presents the planned files and commit messages first and asks for confirmation. Nothing is staged or committed until you approve the plan.

What git commands does the commit workflow use?▼

It uses git status and git diff to inspect changes, git add with specific file paths for staging, git commit for creating commits, and git log --oneline to show the resulting history.