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.
Install
npx skills add lucaspmarie-a11y/claude-skills-vault --skill commitgit clone --depth 1 https://github.com/lucaspmarie-a11y/claude-skills-vault.git /tmp/claude-skills-vault
mkdir -p ~/.claude/skills
cp -r /tmp/claude-skills-vault/plugins/antigravity-awesome-skills-claude/skills/commit ~/.claude/skills/commitPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Sentry Commit Messages Follow these conventions when creating commits for Sentry projects. ## Prerequisites Before committing, always check the current branch: ```bash git branch --show-current ``` **If you're on `main` or `master`, you MUST create a feature branch first** — unless the user explicitly asked to commit to main. Do not ask the user whether to create a branch; just proceed with branch creation. The `create-branch` skill will still propose a branch name for the user to confirm. Use the `create-branch` skill to create the branch. After `create-branch` completes, verify the current branch has changed before proceeding: ```bash git branch --show-current ``` If still on `main` or `master` (e.g., the user aborted branch creation), stop — do not commit. ## Format ``` <type>(<scope>): <subject> <body> <footer> ``` The header is required. Scope is optional. All lines must stay under 100 characters. ## Commit Types | Type | Purpose | |------|---------| | `feat` | New feature | | `fix` | Bug fix | | `ref` | Refactoring (no behavior change) | | `perf` | Performance improvement | | `docs` | Documentation only | | `test` | Test additions or corrections | | `build` | Build system or dependencies | | `ci` | CI configuration | | `chore` | Maintenance tasks | | `style` | Code formatting (no logic change) | | `meta` | Repository metadata | | `license` | License changes | ## Subject Line Rules - Use imperative, present tense: "Add feature" not "Added feature"
Details
- Skill name
commit- Repository
- lucaspmarie-a11y/claude-skills-vault
- Path
plugins/antigravity-awesome-skills-claude/skills/commit/SKILL.md- License
- MIT
- Repo updated
- 6 June 2026
FAQ
What does the Commit skill do?
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.
How do I install the Commit skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add lucaspmarie-a11y/claude-skills-vault --skill commit. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Commit popular?
It lives in lucaspmarie-a11y/claude-skills-vault, which has 5 GitHub stars and 0 forks.
Related skills
Apify Influencer Discovery
5lucaspmarie-a11y/claude-skills-vault
Find and evaluate influencers for brand partnerships, verify authenticity, and track collaboration performance across Instagram, Facebook, YouTube, and TikTok.
00 Andruia Consultant
5lucaspmarie-a11y/claude-skills-vault
Arquitecto de Soluciones Principal y Consultor Tecnológico de Andru.ia. Diagnostica y traza la hoja de ruta óptima para proyectos de IA en español.
10 Andruia Skill Smith
5lucaspmarie-a11y/claude-skills-vault
Ingeniero de Sistemas de Andru.ia. Diseña, redacta y despliega nuevas habilidades (skills) dentro del repositorio siguiendo el Estándar de Diamante.
Comprehensive Review PR Enhance
5lucaspmarie-a11y/claude-skills-vault
Generate structured PR descriptions from diffs, add review checklists, risk assessments, and test coverage summaries. Use when the user says "write a PR description", "improve this PR", "summarize my changes", "PR review", "pull request", or asks to document a diff for reviewers.
PR Review
1priyank766/OpenSource-SKILL
High-signal, maintainer-grade review of an open-source pull request. Use when asked to review a PR, review a diff, look over changes before posting feedback, or when preparing review comments for a GitHub pull request. Applies a weighted 10-point quality filter so only findings scoring 8.0+ are surfaced, and enforces a human contributor voice instead of AI cheerleading. Works for any language or ecosystem. Do NOT use for reviewing your own uncommitted work-in-progress.
Create PR
5lucaspmarie-a11y/claude-skills-vault
Alias for sentry-skills:pr-writer. Use when users explicitly ask for "create-pr" or reference the legacy skill name. Redirects to the canonical PR writing workflow.
Browse the most popular Claude skills, all git & code review skills, or write your own with the skills generator.