committing

Creates git commits with user approval from explicit file paths or auto-discovered changes.

1|Updated Feb 10, 2026
One-click install
npx skills add https://github.com/stefanfaur/roach-marketplace --skill committing-stefanfaur
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: committing
Source: https://github.com/stefanfaur/roach-marketplace/tree/main/roach/skills/committing
Command: npx skills add https://github.com/stefanfaur/roach-marketplace --skill committing-stefanfaur

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Creating clean, well-organized git commits requires inspecting diffs, grouping related changes, and writing meaningful messages, which is tedious and error-prone when done manually. This Skill automates commit creation while keeping you in control through a mandatory approval step. ## Core Features & Use Cases - Explicit File Commits: Provide specific file paths and get scoped diffs analyzed only for those files, with intelligent splitting into logical commits. - Auto-Discovery Mode: Run without arguments to scan all staged and unstaged changes, then receive a proposed grouping by feature, domain, or change type. - Safe Commit Practices: Uses direct git commit <files> -m syntax to avoid accidentally committing unrelated staged files, and never adds AI attribution or co-author lines. - Use Case: After a long coding session with mixed changes across features and configs, invoke the Skill with no arguments to get a proposed multi-commit plan you can approve or adjust before anything is committed. ## Quick Start Commit all my current changes, grouping them into logical commits with clear messages after I approve the plan.

Frequently Asked Questions about committing

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

FAQPage Schema
How do I commit only specific files in git?▼

Use direct commit syntax: git commit <file1> <file2> -m "message". This commits only the listed files without staging anything else, avoiding the risk of including unrelated staged changes that git add followed by git commit would capture.

How to split changes into multiple logical commits?▼

Group files by logical relationship such as same feature, domain, or change type like config versus implementation versus tests. Inspect diffs per group, then create separate commits in order with focused imperative-mood messages explaining why each change was made.

What happens if a file has both staged and unstaged changes?▼

The Skill flags this explicitly before committing, noting that only the staged portion will be committed for that file. You can then decide whether to stage the remaining changes or adjust the proposed grouping.

Does the committing skill add AI attribution to commit messages?▼

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

Can I adjust the proposed commit grouping before execution?▼

Yes. The Skill always presents a commit plan and waits for confirmation. You can request merging commits, excluding files, or rewording messages, and nothing is committed until you approve.