Best use case
commit is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Optionally checks, then commits code to the current or a new feature branch.
Teams using commit should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/commit/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How commit Compares
| Feature / Agent | commit | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Optionally checks, then commits code to the current or a new feature branch.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
When asked to commit code, follow these steps: ## Arguments - `check` (default): Run checks first to lint, build, and test the code. Stop if any checks fail. - `force`: Skip the check step and commit directly. ## Steps 1. Run these bash commands in parallel to understand the current state: - `git status` to see all untracked files - `git diff HEAD` to see both staged and unstaged changes - `git log --oneline -10` to see recent commit messages for style consistency 2. If you are on the `main` branch, create a new feature branch using `git branch` and switch to it. 3. Analyze all changes and draft a commit message: - Summarize the nature of the changes (new feature, enhancement, bug fix, refactoring, test, docs, etc.) - Use the conventional commit format: `type(scope): description` - Keep the first line under 72 characters - Do not commit files that likely contain secrets (.env, credentials.json, etc.) 4. Stage and commit the changes: - Add relevant files using `git add` - Use a plain string for the commit message (do not use HEREDOCs). 5. Report the results including: - The commit hash - The commit message
Related Skills
wallet
Use the wallet tools for all balance, send, and sign operations. Supports both ETH and ERC-20 tokens. The away wallet operates autonomously after setup — the home device does not need to be online.
metamask
Use the MetaMask tools to request and interact with wallet capabilities from the MetaMask capability vendor.
discovery
Use the discovery tools to find and use services through a service matcher. Do not rely on prior knowledge of services, providers, or APIs.
update-changelogs
Updates changelogs for all packages with consumer-facing changes.
push
Pushes the current branch to the remote repository.
pr
Creates a pull request for the current branch.
lint-build-test
How to check code by linting, building, and testing.
glossary
How to add entries to the glossary
evm-wallet-docker-e2e
Run the evm-wallet Docker e2e tests (build, start stack, wait for healthy, test, diagnose failures).
create-package
Create a new monorepo package using the create-package CLI
code-review
How to review code; a pull request, feature branch, local changes etc.
commit
ALWAYS use this skill when committing code changes — never commit directly without it. Creates commits following Sentry conventions with proper conventional commit format and issue references. Trigger on any commit, git commit, save changes, or commit message task.