commit

Stage, commit, and push git changes with a concise message.

Updated May 22, 2026
One-click install
npx skills add https://github.com/kitfunso/claude-config --skill commit-kitfunso
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: commit
Source: https://github.com/kitfunso/claude-config/tree/main/skills/commit
Command: npx skills add https://github.com/kitfunso/claude-config --skill commit-kitfunso

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? This Skill removes the friction of routine git operations by staging, committing, and pushing changes in one step when you do not need a diff review. ## Core Features & Use Cases - Selective Staging: Stage only the files you specify, or all changed files by default. - Concise Commit Messages: Automatically writes a short, clear commit message for the changes. - Push to Current Branch: Pushes the commit directly to the branch you are working on. - Use Case: After finishing a quick fix, say "commit and push" and the changes are staged, committed with a clean message, and pushed without reviewing diffs. ## Quick Start Commit and push all my current changes with a short message.

Frequently Asked Questions about commit

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

FAQPage Schema
How do I commit and push changes in one step?▼

Ask to commit and push, and the skill stages all changed files, writes a concise commit message, and pushes to the current branch. You can also name specific files to stage only those.

How to commit only specific files in git?▼

Specify the files you want staged when invoking the commit, and only those files will be included. If you name no files, all changed files are staged by default.

Does this skill review diffs before committing?▼

No, it commits and pushes without reviewing diffs or touching anything outside the specified files. It is intended for quick commits where you already trust the changes.

What happens when pre-commit hooks fail?▼

If pre-commit hooks fail, the skill asks whether you want to retry with --no-verify to bypass the hooks. It does not bypass hooks automatically without your confirmation.

When should I not use a no-review commit workflow?▼

Avoid it for large or unfamiliar changes where reviewing diffs prevents mistakes, such as before merging to shared branches. Use a diff review or code review workflow instead in those cases.