commit

Stages changes and creates git commits with auto-generated conventional commit messages.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Writing clear, consistent commit messages is tedious and often skipped, leading to messy git histories. This Skill analyzes your current changes, generates conventional commit messages, stages the right files safely, commits, and pushes in one workflow. ## Core Features & Use Cases - Automatic Message Generation: Analyzes the git diff and recent commit history to produce three conventional commit message candidates matching your repo's style. - Safe Staging: Stages specific files instead of git add ., avoiding accidental commits of .env files or credentials. - Commit and Push: Executes the commit with the selected message and pushes to the remote, showing the final commit hash. - Use Case: After finishing a bug fix across several files, invoke the Skill to get a properly formatted message like fix(auth): clear session on app uninstall webhook, commit it, and push without writing the message yourself. ## Quick Start Ask the assistant to commit my current changes with a conventional commit message and push to the remote.

Frequently Asked Questions about commit

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

FAQPage Schema
How do I write a conventional commit message?

Use the format type(scope): description, where type is one of feat, fix, docs, style, refactor, perf, test, build, ci, or chore. Keep the first line under 72 characters and use imperative mood, such as feat(auth): add login rate limiting.

How do I commit changes without staging .env or secret files?

Stage specific files by name with git add instead of using git add . or git add -A. This Skill follows that rule automatically and warns you when uncommitted changes exist in sensitive files.

Does this Skill push to the remote after committing?

Yes, it always runs git push after a successful commit to sync with the remote repository. It also displays the final commit hash and message so you can verify the result.

What happens if there are no changes to commit?

The Skill checks git status first and will not create an empty commit. Instead it informs you that there is nothing to commit, avoiding noise in the repository history.

Can it match my repository's existing commit style?

Yes, it reads the last 10 commits via git log --oneline and generates message candidates that match the repo's existing conventions while still following the conventional commits format.