commit

Groups working-tree changes into logical chunked Git commits with push and pull request modes.

Updated Nov 25, 2024
One-click install
npx skills add https://github.com/cbrostrom/dotfiles --skill commit-cbrostrom
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: commit
Source: https://github.com/cbrostrom/dotfiles/tree/main/stow/agents/.agents/skills/commit
Command: npx skills add https://github.com/cbrostrom/dotfiles --skill commit-cbrostrom

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning a messy working tree into clean, reviewable Git history is tedious: developers often dump everything into one commit or struggle to write consistent messages. This Skill analyzes the full diff, groups changes into meaningful chunks, and writes convention-matching commit messages, with optional push and pull request creation. ## Core Features & Use Cases - Logical Chunking: Groups changed files by concern (feature vs. fix vs. config) into separate commits, staging named files only and never using blanket git add -A. - Convention-Aware Messages: Follows repo instructions first, then matches the last 10 commits' style, falling back to conventional commits; never adds AI attribution trailers. - Three Modes: commit only, commit and push (git push -u origin HEAD), or full flow ending in a gh pull request with a drafted title and body. - Use Case: After a coding session touching eight files across two features, ask to "commit this" and receive two or three clean, reviewable commits with proper messages instead of one monolithic dump. ## Quick Start Ask the assistant to commit this, and it will inspect the diff, propose logical chunks, and create clean conventional commits for your current branch.

Frequently Asked Questions about commit

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

FAQPage Schema
How do I split uncommitted changes into multiple Git commits?▼

Group changed files by concern and stage each group separately with named file paths, then commit each group with its own message. This Skill automates that by analyzing the full diff and proposing logical chunks before committing.

How to write conventional commit messages automatically?▼

The Skill first checks repo instructions like AGENTS.md, then matches the style of the 10 most recent commits, and otherwise falls back to conventional commits format such as type(scope): description. Bodies explain motivation for non-trivial changes.

Can I commit, push, and open a GitHub pull request in one step?▼

Yes, the push and PR mode chunks and commits changes, pushes with git push -u origin HEAD, then uses the gh CLI to check for an existing PR or create a new one with a drafted title and body after your confirmation.

What happens if I run a commit on the main branch or detached HEAD?▼

On the default branch, the Skill warns and asks whether to commit directly or create a feature branch first. In detached HEAD state, it asks you to create a feature branch before proceeding.

Does this add AI attribution or co-author trailers to commits?▼

No, the Skill explicitly forbids attribution lines such as Made-with or Co-authored-by trailers. It verifies the final message with git log and amends if one slipped in, when safe to do so.