Ready to supercharge your AI agents?

Install any skill in seconds. Free to start, no credit card required.

Sentry Commit Messages · aiskillstore | DecimalAI

aiskillstore/commit

SkillScore100Maintained

Helps write conventional commit messages, create atomic commits, and follow git best practices. Use when the agent needs to help with git commits, commit message writing, or git workflow guidance.

DevOpsby aiskillstore

Links this skill to your agents and keeps it current with the author’s updates.

Automatic

Coding pack

1 · One-time — install the CLI (docs ↗)

pip install decimalai

2 · Get the skill — writes .claude/skills/aiskillstore-commit/SKILL.md

decimalai skills pull aiskillstore-commit --out .claude/skills/

No CLI? Get the same file — curl · raw file

curl -fsSL --create-dirs -o .claude/skills/aiskillstore-commit/SKILL.md https://app.decimal.ai/s/aiskillstore-commit/SKILL.md

Raw file: /s/aiskillstore-commit/SKILL.md ↗ · machine-readable summary at /s/aiskillstore-commit.json ↗

In productionGlobal

how this skill behaves on real traffic · last 30 days

No production data for this skill yet — usage numbers appear here once agents start running it.

Anonymized aggregate across every org using this skill — proof from real production use, not a demo.

Does this skill help? · Benchmark: with vs. withoutsign in to run this on your agents

25 test cases from the publisher’s eval.yaml · each run twice on gemini-3.6-flash — with the skill injected, then without · last run 2d ago

Yes — +44% lift · at higher cost+30% tokens0% turns100% of whole cases pass with skill (25/25)

Test case	Without → With	Effect	Δ tokens	Δ turns
case-04	✗→✓	▲ Improved	27%	0%
case-01	✗→✓	▲ Improved	68%	0%
case-02	✗→✓	▲ Improved	52%	0%
case-03	✗→✓	▲ Improved	56%	0%
case-07	✗→✓	▲ Improved	-11%	0%

Showing 5 of 25 cases

SkillSafety

✓ 3 of 3 passed

Code scan15 of 15 checks clean

0 critical · 0 warning · 0 info — scanner v5 — 8/27/2026

live_secretremote_code_executionreverse_shelldata_exfiltrationssrf_metadataagent_snoopinganti_refusaldestructive_commandsobfuscated_unicodeunicode_homoglyphopaque_blobsuspicious_urltool_overreachtrigger_abuseprompt_injection_phrasing

IntentSafe

LLM judge · does the skill do what it claims

ContentClean

LLM judge · policy & harmful-content review

Source

Imported

aiskillstore / marketplace

skills/0xmsc/commit/SKILL.md

View on GitHub ↗

Imported 8/27/2026Version v5

Skill contents

SKILL.md

Sentry Commit Messages

Follow these conventions when creating commits for Sentry projects.

When to Use This Skill

Use this skill when:

Committing code changes
Writing commit messages
Formatting git history
Following Sentry commit conventions
Referencing Sentry issues in commits

Prerequisites

Before committing, ensure you're working on a feature branch, not the main branch.

bash
# Check current branch
git branch --show-current

If you're on main or master, create a new branch first:

bash
# Create and switch to a new branch
git checkout -b <type>/<short-description>

Branch naming should follow the pattern: <type>/<short-description> where type matches the commit type (e.g., feat/add-user-auth, fix/null-pointer-error, ref/extract-validation).

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-123

Fixes closes the issue when merged
Refs links without closing

AI-Generated Changes

When changes were primarily generated by a coding agent (like Claude Code), include the Co-Authored-By attribution in the commit footer:

Co-Authored-By: Claude <noreply@anthropic.com>

This is the only indicator of AI involvement that should appear in commits. Do not add phrases like "Generated by AI", "Written with Claude", or similar markers in the subject, body, or anywhere else in the commit message.

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-5678
Co-Authored-By: Claude <noreply@anthropic.com>

Feature 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-1234

Refactor

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-9999

Revert 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

Sentry Commit Messages

Want to see if aiskillstore/commit would activate on your phrasing? Try it before you install — no LLM call, no signup.

Latest benchmark · publisher runVerified

8/27/2026, 06:34 UTC · 25 cases

Lift

+44%

100% vs 56%

Agent turns

1.0 vs 1.0

Tokens

+30%

1,737.92 vs 1,340.68

fail → pass · 11pass → pass · 14

Per-case results (25)

Case	Status	Duration (ms)			Turns			Tokens			Tool calls
Case	Status	Without	With	Δ	Without	With	Δ	Without	With	Δ	Without	With	Δ
case-04 I optimized the SQL queries in the event stream processor to decrease latency by 40%. The issue key is LINEAR-OPS-99, but this work does not close the ticket, it only relates to it. Draft the commit message following Sentry guidelines. Many devs put 'perf(db): optimized query' with lowercase and period; should I follow that?	fail→pass	7,854	4,789	-39%	1	1	0%	1,559	1,973	+27%	0	0	—
case-01 I just refactored the authentication middleware in our backend service to remove redundant validation checks. This resolves SENTRY-8821, and I built this with assistance from Claude Code. Could you draft the complete Git commit message for me following our project's repository conventions?	fail→pass	8,240	5,727	-30%	1	1	0%	1,261	2,120	+68%	0	0	—
case-02 I fixed a bug where unexpected empty payload responses in the alert notification pipeline caused worker processes to crash. It resolves GH-4521. Can you suggest the proper branch creation command and write out the full commit message based on our team's commit standards?	fail→pass	6,596	4,582	-31%	1	1	0%	1,284	1,946	+52%	0	0	—
case-03 I introduced a new filtering dropdown in the project settings dashboard that lets users filter error events by environment, which resolves issue SENTRY-4102. Please write the formatted Git commit message for this update according to our project's guidelines.	fail→pass	6,460	4,460	-31%	1	1	0%	1,282	2,003	+56%	0	0	—
case-05 I updated the repository setup documentation to include instructions for setting up local Redis queues. I want to commit this using our Sentry repo standards. Should I write 'doc: updated readme' or 'docs(readme): Add Redis queue setup instructions'?	pass→pass	6,248	4,658	-25%	1	1	0%	1,191	1,871	+57%	0	0	—
case-06 I added unit tests for the webhook signature verification helper. I'm tempted to use 'test: added tests for webhook signature.' as the subject line. How should this be formatted for Sentry repos?	pass→pass	6,796	4,339	-36%	1	1	0%	1,274	1,843	+45%	0	0	—
case-07 We upgraded the urllib3 dependency in pyproject.toml to address a security advisory. Should I use 'chore: upgrade urllib3' or is there a specific Sentry commit type for build system and dependency updates?	fail→pass	23,149	4,571	-80%	1	1	0%	1,963	1,754	-11%	0	0	—
case-08 I modified our GitHub Actions workflow file to run integration tests on pull requests. What commit type prefix should be used according to Sentry standards?	pass→pass	6,901	2,702	-61%	1	1	0%	1,206	1,471	+22%	0	0	—
case-09 I ran Black and Prettier across the codebase to fix formatting without changing any logic. Some team members label this 'chore: format code'. What is the Sentry conventional commit type for pure code style changes?	pass→pass	5,927	2,642	-55%	1	1	0%	1,135	1,475	+30%	0	0	—
case-10 I wrote a feature with Claude Code that adds Slack thread replies for alerts. I want to put 'Generated by Claude Code' in the commit body and 'Co-authored-by: Claude <noreply@anthropic.com>' in the footer. Does Sentry allow AI markers in the body?	fail→pass	7,993	3,414	-57%	1	1	0%	1,416	1,702	+20%	0	0	—
case-11 I made progress on issue SENTRY-3344 by adding the database migration, but the full feature isn't finished yet so SENTRY-3344 should NOT be closed. I usually put 'Fixes SENTRY-3344' or 'Addresses SENTRY-3344'. What is the exact keyword for linking without closing under Sentry standards?	pass→pass	8,002	2,580	-68%	1	1	0%	1,491	1,562	+5%	0	0	—
case-12 I wrote a commit header 'feat(auth): Added support for multi-factor authentication via TOTP tokens and backup codes for enterprise users.' for a Sentry project. What subject line rules does this break?	pass→pass	9,770	4,747	-51%	1	1	0%	1,824	1,929	+6%	0	0	—
case-13 I am about to start working on fixing a null pointer bug in Sentry's event intake pipeline. I am currently on the main branch. What git commands should I run to check my branch and switch to a properly named branch per Sentry guidelines?	pass→pass	5,502	3,363	-39%	1	1	0%	1,032	1,663	+61%	0	0	—
case-23 I am opening a Pull Request on GitHub for a Sentry repository. Can you draft a standard PR description body with sections like 'Summary', 'Test Plan', and 'Checklist'?	pass→pass	8,647	6,908	-20%	1	1	0%	1,485	2,105	+42%	0	0	—
case-14 When writing the commit message body for a complex refactoring in Sentry, should I detail step-by-step how the code functions line-by-line, or focus on what and why the change was made?	pass→pass	12,900	4,475	-65%	1	1	0%	2,043	1,759	-14%	0	0	—
case-15 We are removing all deprecated v1 endpoints from the Sentry API, which will break client applications that haven't migrated to v2. I want to write a commit message. Should I put [BREAKING CHANGE] in the subject line or use special header syntax and footer keywords for Sentry commits?	pass→pass	7,993	3,968	-50%	1	1	0%	1,345	1,813	+35%	0	0	—
case-16 I need to revert a previous Sentry commit abc123def456 that added a bad API endpoint. Should I label it [REVERT] in the subject or use standard revert syntax with the original commit identifier in the body?	fail→pass	7,762	3,267	-58%	1	1	0%	1,378	1,598	+16%	0	0	—
case-17 I am adding an endpoint to the Sentry API service. Should the subject header format be 'feat - api: Add endpoint', 'feat/api: Add endpoint', or 'feat(api): Add endpoint'?	pass→pass	6,103	3,300	-46%	1	1	0%	1,102	1,585	+44%	0	0	—
case-18 What are the line character length limits for the subject line header and overall commit message lines according to Sentry commit guidelines?	pass→pass	5,802	1,768	-70%	1	1	0%	952	1,277	+34%	0	0	—
case-19 I fixed an issue tracked in Linear as LINEAR-ENG-456. Should I put 'Closes LINEAR-ENG-456' or 'Fixes LINEAR-ENG-456' or 'Refs LINEAR-ENG-456' if I want to resolve the issue upon merging?	fail→pass	7,069	3,285	-54%	1	1	0%	1,330	1,602	+20%	0	0	—
case-20 I am fixing GitHub issue GH-789 in a Sentry repository. Can I write 'Fixes GH-789' or 'Fixes #789' in the commit footer?	fail→pass	7,919	2,399	-70%	1	1	0%	1,319	1,405	+7%	0	0	—
case-21 I am updating the CODEOWNERS file and .github repository templates. What Sentry commit type should I use?	fail→pass	7,122	3,214	-55%	1	1	0%	1,172	1,524	+30%	0	0	—
case-22 I am updating the LICENSE file text to update the copyright year across the Sentry codebase. What commit type prefix applies?	fail→pass	5,808	2,349	-60%	1	1	0%	950	1,350	+42%	0	0	—
case-24 I am preparing the CHANGELOG.md entry for Sentry release v23.5.0 following Keep a Changelog conventions. Please draft the changelog section for added and fixed items.	pass→pass	10,478	7,650	-27%	1	1	0%	1,661	2,409	+45%	0	0	—
case-25 I need to create an annotated Git tag on main for version 2.4.0 in our Sentry backend repository. What is the standard git tag CLI command to create an annotated tag with a message?	pass→pass	4,402	3,988	-9%	1	1	0%	862	1,709	+98%	0	0	—

These cases were also screened by the skill’s intent / safety pass.See the Trust review ↗Reproduce this benchmark in Colab ↗

How this skill was measured

DecimalAI ran this skill against gemini-3.6-flash twice over the same eval suite — once with the skill loaded and once without — and compared the two runs case by case. 25 cases were attempted. The headline lift of +44 percentage points is the difference between those two pass rates over the 25 comparable cases.

Model measured: gemini-3.6-flash
Graded by: gemini-3.6-flash
Grading method: judged
Verification: verified
Pass rate without the skill: 56%
Pass rate with the skill: 100%
Cases attempted: 25
Cases counted toward lift: 25
Cases that regressed: 0
Skill version measured: v5
Run completed: 8/27/2026, 06:34 UTC

Measured example — same prompt, with vs. without the skill · from the benchmark run · case case-04

Prompt

I optimized the SQL queries in the event stream processor to decrease latency by 40%. The issue key is LINEAR-OPS-99, but this work does not close the ticket, it only relates to it. Draft the commit message following Sentry guidelines. Many devs put 'perf(db): optimized query' with lowercase and period; should I follow that?

Without the skill loaded, the model failed this case. With it loaded, the same prompt on the same model passed. This is one improved case from the latest verified run; every case, including any that regressed, is in the table above.

Show both answers

SkillScore blends 4 signals1 of 4 complete

BenchmarkPass rate WITH skill on a verified run100

Live evalNeeds ≥20 evaluated traces in 30 days

AI ratingNeeds ≥10 rated traces

AdoptionNeeds ≥10 serves across ≥2 orgs in 30 days

Efficiency · separate axis (at equal correctness)+0% turns+32% tokens

Shown for transparency; not credited unless a verified run shows no correctness regression.

Backed by 1 of 4 signals — each added signal makes the score more robust.

Verified on gemini-3.6-flash · re-tested 2 days ago

Model	Method	Date	Lift
gemini-3.6-flash	verified	8/21/2026	-9%

Other measured skills in the registry, with their headline benchmark lift.