commit
A standardized tool for committing and pushing repository changes.
Install
mkdir -p .claude/skills/commit-vultisig && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/12222" && unzip -o skill.zip -d .claude/skills/commit-vultisig && rm skill.zipInstalls to .claude/skills/commit-vultisig
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Stage, commit, and optionally push changes. Use after completing a task.Key capabilities
- →Review current changes in the working tree and staged area
- →Stage specific files for commit
- →Create a commit with a Conventional Commit message
- →Optionally push the committed changes to the remote repository
- →Ensure commit messages adhere to a 72-character limit for the first line
- →Include a `Co-Authored-By` trailer in commit messages
How it works
The skill guides the user to review changes, stage specific files, create a commit with a structured message, and optionally push the commit.
Inputs & outputs
When to use commit
- →Stage and commit changes
- →Push repository updates
About this skill
Commit Changes
Workflow
1. Review Changes
git status
git diff --staged
git diff
2. Stage Files
Stage specific files (never git add . or git add -A):
git add <specific-files>
3. Create Commit
git commit -m "$(cat <<'EOF'
feat: add TRC20 token transfer support
Co-Authored-By: Claude <[email protected]>
EOF
)"
4. Push (if requested)
git push
Rules
- Keep the first line under 72 characters
- Add body for complex changes
- Always include
Co-Authored-Bytrailer - Never commit
.env, credentials, or secrets - Never use
--no-verifyunless explicitly asked
When not to use it
- →When committing sensitive information like `.env` files or credentials
- →When the user wants to bypass git hooks with `--no-verify`
- →When the user wants to use `git add .` or `git add -A`
Limitations
- →Never commit `.env`, credentials, or secrets
- →Never use `--no-verify` unless explicitly asked
- →Never `git add .` or `git add -A`
How it compares
This skill enforces a structured commit process by requiring specific file staging and Conventional Commit messages, unlike a general `git commit` that allows for less disciplined practices.
Compared to similar skills
commit side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| commit (this skill) | 0 | 5mo | Review | Beginner |
| resolve-conflicts | 81 | 8mo | Review | Intermediate |
| dependency-upgrade | 26 | 5mo | Review | Intermediate |
| openspec-onboard | 10 | 6mo | Review | Beginner |
Try saying
Example prompts that trigger this skill in your AI assistant.
You might also like
resolve-conflicts
antinomyhq
Use this skill immediately when the user mentions merge conflicts that need to be resolved. Do not attempt to resolve conflicts directly - invoke this skill first. This skill specializes in providing a structured framework for merging imports, tests, lock files (regeneration), configuration files, and handling deleted-but-modified files with backup and analysis.
dependency-upgrade
wshobson
Manage major dependency version upgrades with compatibility analysis, staged rollout, and comprehensive testing. Use when upgrading framework versions, updating major dependencies, or managing breaking changes in libraries.
openspec-onboard
studyzy
Guided onboarding for OpenSpec - walk through a complete workflow cycle with narration and real codebase work.
codex-cli-bridge
alirezarezvani
Bridge between Claude Code and OpenAI Codex CLI - generates AGENTS.md from CLAUDE.md, provides Codex CLI execution helpers, and enables seamless interoperability between both tools
skill-sync
KyleKing
Syncs Claude Skills with other AI coding tools like Cursor, Copilot, and Codeium by creating cross-references and shared knowledge bases. Invoke when user wants to leverage skills across multiple tools or create unified AI context.
git-commits
bonny
Create well-structured git commits in logical chunks following best practices