Commit
Use for every request to commit changes or draft a commit message. Creates Sentry-style conventional commits with issue references.
Install
/plugin marketplace add getsentry/skillsThe repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.
npx skills add getsentry/skills --skill commitgit clone --depth 1 https://github.com/getsentry/skills.git /tmp/skills
mkdir -p ~/.claude/skills
cp -r /tmp/skills/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 ## Before Committing ```bash git branch --show-current ``` If the branch is `main` or `master`, create a feature branch unless the user explicitly requested a direct commit. Re-check the branch and stop if it is still `main` or `master`. Commit one coherent, independently reviewable change at a time. ## Message Rules Use: ```text <type>(<scope>): <subject> <optional body> <optional footer> ``` - Scope is optional. Add `!` before `:` for a breaking change. - Write the subject in imperative, present tense; capitalize it, omit the trailing period, and keep it at 70 characters or fewer. - Keep every line under 100 characters. - Use the body only when useful. Explain what changed and why, including previous behavior or motivation when it helps. - Never include customer or organization names, user emails, support ticket contents, secrets, or PII. Describe the technical symptom instead. Allowed types: `feat`, `fix`, `ref`, `perf`, `docs`, `test`, `build`, `ci`, `chore`, `style`, `meta`, `license`, and `revert`. Use `ref` for refactoring without behavior changes, `style` for formatting without logic changes, and `meta` for repository metadata. ## Footers - `Fixes <issue>` closes an issue when merged. - `Refs <issue>` links an issue without closing it. - For breaking changes, add `BREAKING CHANGE: <impact>`. ## Creating the Commit Use separate `-m` arguments for paragraphs and footers. Never put literal
Details
- Skill name
commit- Repository
- getsentry/skills
- Path
skills/commit/SKILL.md- License
- Apache-2.0
- Repo updated
- 14 November 2026
- Listed in
- heilcheng/awesome-agent-skills
FAQ
What does the Commit skill do?
Use for every request to commit changes or draft a commit message. Creates Sentry-style conventional commits with issue references.
How do I install the Commit skill?
Claude Code plugin: /plugin marketplace add getsentry/skills. 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 getsentry/skills, which has 1,179 GitHub stars and 70 forks, and is included in 1 curated skill list.
Related skills
Doc Coauthoring
1.2kgetsentry/skills
Guide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks.
Brand Guidelines
1.2kgetsentry/skills
Write copy following Sentry brand guidelines. Use when writing UI text, error messages, empty states, onboarding flows, 404 pages, documentation, marketing copy, or any user-facing content. Covers both Plain Speech (default) and Sentry Voice tones.
Code Simplifier
1.2kgetsentry/skills
Simplifies and refines code for clarity, consistency, and maintainability while preserving all functionality. Use when asked to "simplify code", "clean up code", "refactor for clarity", "improve readability", or review recently modified code for elegance. Focuses on project-specific best practices.
Gh Review Requests
1.2kgetsentry/skills
Fetch unread GitHub notifications for open PRs where review is requested from a specified team or opened by a team member. Use when asked to "find PRs I need to review", "show my review requests", "what needs my review", "fetch GitHub review requests", or "check team review queue".
Comet Verify
3.3krpamis/comet
Comet Phase 4: Verify and Close. Invoke with /comet-verify. Verify implementation matches design, handle development branch.
Iterate PR
1.2kgetsentry/skills
Iterate on a PR until actionable CI passes and high/medium review feedback is addressed. Use for PR CI failures, review feedback, or green-check loops; do not wait for human approval, draft status, or merge gates.
Browse the most popular Claude skills, all git & code review skills, or write your own with the skills generator.