Write Sentry Commit Messages
Teams lose time fixing vague or inconsistent commit history. This skill helps Claude, Codex, and Claude Code draft Sentry-style conventional commits with clear issue references.
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Review the Skillstore skill "commit" from https://skillstore.io/skills/getsentry-commit.md and its manifest at https://skillstore.io/api/skills/getsentry-commit/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.Your Agent should still show its plan and request any confirmation required by the security policy.
Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.
Using "commit". A deleted user can return null and crash the dashboard. Issue SENTRY-5678 should close on merge.
Expected outcome:
fix(api): Handle null response in user endpoint
Add a null check before reading deleted account properties. This prevents dashboard crashes for removed users.
Fixes SENTRY-5678
Using "commit". Alert updates should reply in the original Slack thread. Link GH-1234 without closing it.
Expected outcome:
feat(alerts): Add Slack thread replies for alert updates
Post updates and resolutions to the original Slack thread so related notifications stay grouped.
Refs GH-1234
Using "commit". A previous feature commit must be reverted because it caused production performance issues.
Expected outcome:
revert: feat(api): Add new endpoint
This reverts the previous endpoint change.
Reason: Caused performance regression in production.
All static findings appear to be false positives from Markdown backticks, commit message examples, and one documentation link. No prompt injection, malicious intent, secret handling, or executable skill code was found in SKILL.md.
Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.
https://skillstore.io/skills/getsentry-commit/audits/7?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report[](https://skillstore.io/skills/getsentry-commit?utm_source=security_passport_badge)<a href="https://skillstore.io/skills/getsentry-commit?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/getsentry-commit/security.svg" alt="Skillstore security assessment" loading="lazy"></a><iframe src="https://skillstore.io/embed/skills/getsentry-commit.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>getsentry. (2026). commit security audit report (audit version 7) [Author version unspecified]. Skillstore. https://skillstore.io/skills/getsentry-commit/audits/7@techreport{getsentry-getsentry-commit-2026,
author = {getsentry},
title = {commit security audit report (audit version 7)},
institution = {Skillstore},
year = {2026},
number = {7},
url = {https://skillstore.io/skills/getsentry-commit/audits/7},
note = {Author version unspecified}
}cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "commit security audit report (audit version 7)"
version: "unspecified"
type: report
authors:
- name: "getsentry"
date-released: "2026-07-06"
url: "https://skillstore.io/skills/getsentry-commit/audits/7"
identifiers:
- type: other
value: "skillstore:getsentry-commit:audit:7"
description: "Skillstore immutable audit report identifier"
Each author remains a separate installable skill. The recommended variant is ranked by Skillstore evidence.
Why this variant is first
0xmsc-commit
2026-09-09
davila7-commit
2026-09-09
sickn33-commit
2026-09-09
davidopdebeeck-commit
2026-09-09
codename-11-commit
2026-09-09
getsentry-commit
2026-09-09
Draft a conventional commit message that explains a small code change and links the right issue.
Rewrite local commit messages so reviewers see consistent types, scopes, and subjects.
Create commit text for breaking changes, fixes, or refactors that must be easy to audit later.
Write a Sentry-style commit message for this change: [describe the change]. Include a suitable type and concise subject.
Create a Sentry commit message for [change]. Use scope [scope] and reference issue [issue ID] without closing it.
Improve this commit message to follow Sentry conventions: [paste message]. Keep the meaning and make each line under 100 characters.
Write a Sentry-style breaking change commit for [change]. Include motivation, migration impact, and the correct footer format.
Author
getsentryLicense
MIT
Skillstore revision
r1
Version notice
The author did not declare a version.
Ref
a06681402992ceae98ba04d54cfd4ab004862696
Maintenance freshness
7/18/2026
Usage
3 downloads · 305 views
File structure
📄 SKILL.md
Review Code with Sentry Practices
Pull request reviews often miss risks across correctness, security, performance, and testing. This skill gives Claude, Codex, and Claude Code a structured Sentry review checklist.
Clean Up AI-Generated Code Changes
AI-assisted branches often include extra comments, unnecessary defensive code, and weak type workarounds. This skill reviews the branch diff and removes changes that do not match the surrounding code style.
Create Sentry-Style Pull Requests
Writing clear pull requests takes context and review discipline. This skill guides Claude, Codex, and Claude Code through Sentry-style PR preparation.
Review Branch Changes for Bugs
Branch reviews often miss security defects, regressions, and untested edge cases. This skill guides Claude, Codex, and Claude Code through a structured audit.
Iterate Pull Requests Until CI Passes
Pull request fixes often require repeated CI checks, review updates, and careful commits. This skill guides Claude, Codex, or Claude Code through a controlled feedback, fix, push, and wait cycle.
Audit Claude Code Permissions
Unsafe or missing Claude Code permissions can slow repository setup and create avoidable risk. This skill inspects project tooling and proposes settings that match detected files and services.
Create Conventional Git Commits
by 21pounder
Manual commit preparation can miss staged changes, message style, or sensitive files. This skill reviews git state and helps create clear conventional commits.
Write Conventional Commits from Staged Changes
by justhandledlabs
Writing accurate conventional commits from complex staged changes takes time and can produce inconsistent results. This skill inspects staged Git changes and recommends a concise, scoped commit message.
Write Better Git Commit Messages
by Chemiseblanc
Inconsistent commit messages make reviews and release notes harder to scan. This skill formats concise Conventional Commit summaries with clear 72-column bodies.
Create Review-Ready Git Commits
by softaworks
Messy staging and weak messages slow code review. This skill guides selective staging, commit splitting, Conventional Commits messages, and verification.
Master Advanced Git Workflows
by AutumnsGrove
Complex Git maintenance can make history changes and conflict resolution difficult. This skill provides structured guidance, recovery steps, and an optional local helper for common advanced workflows.
Draft Git Commit Messages From Staged Changes
by AbeJitsu
Writing commit messages from staged changes takes time and can miss important context. This skill collects git status and diff details so AI can draft a clear message.