commit
Create Sentry-Style Commit Messages
Teams need consistent commit history that follows Sentry conventions. This skill formats concise headers, useful bodies, and supported issue references.
Install with my Agent
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Review the Skillstore skill "commit" from https://skillstore.io/skills/davila7-commit.md and its manifest at https://skillstore.io/api/skills/davila7-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.
Agent-readable resources
Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.
Test it
Using "commit". Fix a crash when a deleted user returns a null API response. Close SENTRY-5678.
Expected outcome:
Suggested message: fix(api): Handle null response for deleted users. Explain the crash prevention, then add Fixes SENTRY-5678.
Using "commit". Move duplicate validation into a shared module without changing behavior.
Expected outcome:
Suggested message: ref: Extract shared validation logic. State that duplicate endpoint validation moved with no behavior change.
Using "commit". Remove deprecated version one endpoints and direct clients to version two.
Expected outcome:
Suggested message: feat(api)!: Remove deprecated v1 endpoints. Include migration guidance and a BREAKING CHANGE footer.
Security Audit
SafeAll 27 command findings are Markdown fences or inline code formatting, not executable shell or Ruby syntax. The URL is a documentation link and causes no network request. No prompt injection or harmful intent was found.
Risk Factors
โ๏ธ External commands (27)
๐ Network access (1)
Share & cite this report
Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.
Copy report link
https://skillstore.io/skills/davila7-commit/audits/10?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown badge
[](https://skillstore.io/skills/davila7-commit?utm_source=security_passport_badge)HTML badge
<a href="https://skillstore.io/skills/davila7-commit?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/davila7-commit/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Embed card
<iframe src="https://skillstore.io/embed/skills/davila7-commit.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>Academic citations (APA ยท BibTeX ยท CFF)
APA citation
davila7. (2026). commit security audit report (audit version 10) [Author version unspecified]. Skillstore. https://skillstore.io/skills/davila7-commit/audits/10BibTeX citation
@techreport{davila7-davila7-commit-2026,
author = {davila7},
title = {commit security audit report (audit version 10)},
institution = {Skillstore},
year = {2026},
number = {10},
url = {https://skillstore.io/skills/davila7-commit/audits/10},
note = {Author version unspecified}
}CITATION.cff
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 10)"
version: "unspecified"
type: report
authors:
- name: "davila7"
date-released: "2026-07-23"
url: "https://skillstore.io/skills/davila7-commit/audits/10"
identifiers:
- type: other
value: "skillstore:davila7-commit:audit:10"
description: "Skillstore immutable audit report identifier"
Compare variants
6 installable variantsEach author remains a separate installable skill. The recommended variant is ranked by Skillstore evidence.
Why this variant is first
0xmsc-commit
2026-10-12
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
Skillstore Score
Why this score Evidence Confidence: HighWhat You Can Build
Standardize daily commits
Turn a change summary into a consistent Sentry-style commit message.
Improve review context
Create commit bodies that explain motivation and previous behavior for reviewers.
Prepare release history
Format issue references and breaking-change notices for a clear project history.
Try These Prompts
Write a Sentry-style commit message for this change: [change]. Choose the correct type and keep the subject under 70 characters.
Create a scoped commit message for [change]. Explain why it matters and add [Fixes or Refs] for issue [identifier].
Write a breaking-change commit for [change]. Include migration guidance, a BREAKING CHANGE footer, and the relevant issue reference.
Split these changes into independently reviewable commits, then write a Sentry-style message for each: [changes]. Add issue references where appropriate.
Best Practices
- Describe one stable, independently reviewable change per commit.
- Use an imperative subject and explain what changed and why.
- Confirm whether an issue footer should close or only reference the issue.
Avoid
- Do not combine unrelated changes in one commit message.
- Do not use vague subjects that hide the affected component or behavior.
- Do not add Fixes when the commit should only reference an issue.
Frequently Asked Questions
Does this skill create the Git commit?
Which commit types are supported?
Can I include a scope?
How are issue references handled?
Can it format breaking changes?
What are the line length limits?
Developer Details
Author
davila7License
MIT
Skillstore revision
r2
Version notice
The author did not declare a version.
Repository
https://github.com/davila7/claude-code-templates/tree/main/cli-tool/components/skills/sentry/commitRef
c43861a65bb95efcae259cd161c9d6f4dc7eec6f
Maintenance freshness
7/24/2026
Usage
6 downloads ยท 205 views
File structure
๐ SKILL.md