Commit
- 438 installs
- 30.1k repo stars
- Updated August 4, 2026
- davila7/claude-code-templates
commit is a Claude Code skill that generates conventional commit messages with Sentry-style issue references from staged git changes for developers who need consistent, traceable version history.
About
commit is a Claude Code skill from davila7/claude-code-templates that formats git commits using conventional commits with Sentry-specific issue references. The skill enforces a required header pattern of type, optional scope, and subject under 100 characters, plus body and footer sections. Supported commit types include feat, fix, ref, perf, and docs, each mapped to a clear purpose so agents and developers produce readable history during active feature work. Developers reach for commit when staging changes and needing standardized messages that link work to tracked issues without manually drafting headers and footers.
- Conventional commit formatting
- Staged diff summarization
- Scope and type inference
- Team message standard enforcement
Commit by the numbers
- 438 all-time installs (skills.sh)
- Ranked #113 of 733 Git & Pull Requests skills by installs in the Skillselion catalog
- Data as of Aug 5, 2026 (Skillselion catalog sync)
npx skills add https://github.com/davila7/claude-code-templates --skill commitAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 438 |
|---|---|
| repo stars | ★ 30.1k |
| Last updated | August 4, 2026 |
| Repository | davila7/claude-code-templates ↗ |
How do you write Sentry-style conventional commits?
Generate conventional commit messages from staged changes so agents and developers keep readable, traceable git history during active feature work.
Who is it for?
Developers on Sentry projects who want agents to draft conventional commits that stay under 100 characters per line.
Skip if: Teams that do not use conventional commits or Sentry issue linking and prefer free-form commit messages.
When should I use this skill?
The user stages code changes, asks for a commit message, or requests conventional commit formatting with issue references.
What you get
Formatted commit header, body, and footer ready for git commit with typed scope and issue references.
- conventional commit message
- typed commit header
By the numbers
- Enforces a 100-character maximum per commit line
- Defines five primary commit types: feat, fix, ref, perf, docs
Files
Sentry Commit Messages
Follow these conventions when creating commits for Sentry projects.
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"
- Capitalize the first letter
- No period at the end
- Maximum 70 characters
Body Guidelines
- Explain what and why, not how
- Use imperative mood and present tense
- Include motivation for the change
- Contrast with previous behavior when relevant
Footer: Issue References
Reference issues in the footer using these patterns:
Fixes GH-1234
Fixes #1234
Fixes SENTRY-1234
Refs LINEAR-ABC-123Fixescloses the issue when mergedRefslinks without closing
Examples
Simple fix
fix(api): Handle null response in user endpoint
The user API could return null for deleted accounts, causing a crash
in the dashboard. Add null check before accessing user properties.
Fixes SENTRY-5678Feature with scope
feat(alerts): Add Slack thread replies for alert updates
When an alert is updated or resolved, post a reply to the original
Slack thread instead of creating a new message. This keeps related
notifications grouped together.
Refs GH-1234Refactor
ref: Extract common validation logic to shared module
Move duplicate validation code from three endpoints into a shared
validator class. No behavior change.Breaking change
feat(api)!: Remove deprecated v1 endpoints
Remove all v1 API endpoints that were deprecated in version 23.1.
Clients should migrate to v2 endpoints.
BREAKING CHANGE: v1 endpoints no longer available
Fixes SENTRY-9999Revert Format
revert: feat(api): Add new endpoint
This reverts commit abc123def456.
Reason: Caused performance regression in production.Principles
- Each commit should be a single, stable change
- Commits should be independently reviewable
- The repository should be in a working state after each commit
References
Related skills
Caveman CommitGenerate terse, Conventional Commits messages that preserve intent without fluff or AI attribution.272k94k
Resolving Merge ConflictsQuickly understand, resolve, and commit merge conflicts without losing work or breaking their flow.183k193kGit Guardrails Claude CodePrevent Claude Code from accidentally running destructive git commands like force push, hard reset, or clean.175k193k
Using Git WorktreesGuarantee every new feature or implementation task runs inside a clean, isolated workspace without polluting the main branch or current working directory.149k263k
Git CommitGenerate accurate conventional commit messages and intelligently stage files directly from natural language requests.40.6k37.2k
Resolve Merge ConflictsQuickly understand and resolve Git merge conflicts without losing context or breaking changes.16.5k148How it compares
Pick commit over generic writing skills when you need Sentry-linked conventional commit headers generated directly from staged git changes.
FAQ
What commit format does the commit skill use?
The commit skill follows conventional commits with a required header of type, optional scope, and subject, plus body and footer sections. All lines must stay under 100 characters, matching Sentry project conventions.
Which commit types does commit support?
The commit skill supports feat for new features, fix for bug fixes, ref for refactors, perf for performance changes, and docs for documentation-only updates, each with a defined purpose in the Sentry table.