skills.rest
redblacktree
redblacktreeCOMMUNITY
Explore all skills by this author →
GitHub

source-command-ff-commit

Creates atomic git commits from session changes without Codex attribution.

1|1|Updated Feb 3, 2026
Search Tags:#git#code review#version control#workflow automation#commit#commit message
One-click install
npx skills add https://github.com/redblacktree/fastflow --skill source-command-ff-commit-redblacktree
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: source-command-ff-commit
Source: https://github.com/redblacktree/fastflow/tree/main/.agents/skills/source-command-ff-commit
Command: npx skills add https://github.com/redblacktree/fastflow --skill source-command-ff-commit-redblacktree

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When an AI coding agent finishes a work session, the resulting changes still need to be reviewed, grouped, and committed to git. This Skill automates that final step while ensuring commit messages contain no AI attribution, co-author lines, or generated-with footers, so the git history reads as if the user wrote it. ## Core Features & Use Cases - Change Analysis: Runs git status and git diff to understand exactly what changed during the session before committing. - Logical Commit Grouping: Splits changes into focused, atomic commits using targeted git add of specific files rather than blanket staging. - Clean Commit Messages: Writes imperative-mood messages focused on why changes were made, with no co-author or Codex attribution lines. - Use Case: After a fastflow workflow finishes implementing a feature, invoke this Skill to turn the working-tree changes into one or more well-described commits ready for review or a pull request. ## Quick Start Ask the agent to run the ff_commit command to commit the changes made in this session.

Frequently Asked Questions about source-command-ff-commit

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

FAQPage Schema
How do I commit changes made by an AI coding agent?▼

Invoke the ff_commit command after the session ends. The agent runs git status and git diff to review changes, groups related files into logical commits, and creates them with descriptive imperative-mood messages.

How do I remove Codex attribution from git commits?▼

This Skill explicitly forbids co-author lines, Generated-with-Codex footers, and any AI attribution in commit messages. Commits are authored solely by the user, so the git history contains no trace of agent involvement.

Does it stage all files with git add -A?▼

No. The Skill stages specific files individually with git add and never uses -A or the dot shorthand. This keeps each commit focused and prevents unrelated or unintended files from being included.

Will it ask for confirmation before committing?▼

No. The instructions direct the agent to execute commits immediately without asking for confirmation, since the user explicitly requested the commit. It shows the result afterward with git log --oneline.

When should changes be split into multiple commits?▼

Split commits when the session produced unrelated changes, such as a feature plus a bug fix. The Skill groups files that belong together into atomic commits, each with its own message explaining why the change was made.

Related Skills

Explore More Software Engineering Skills→
kaosnyrbkaosnyrb
12

commit

Stage and commit Git changes with a diff-derived message.

Community
Intermediate
tachiiri-orgtachiiri-org

release

Create a pull request from the dev branch to main after verifying branch and remote state.

Official
Intermediate
jonaseck2jonaseck2
2

commit

Stage related files and create commits with pre-commit checks and release-aware updates.

Community
Advanced
chasebuildchasebuild
15

auto-git-commit

Stage changes with git add -p and generate atomic commit messages.

Official
Intermediate