Skip to content
Skills Library
Programming · Writing

sentry-commit-messages

/sentry-commit-messages

Create commit messages following Sentry conventions with conventional commits and issue references. Use when committing code changes, writing commit messages, or formatting git history with Fixes/Refs patterns.

Author
zfogg ↗
Repository
ascii-chat ↗
Licence
MIT
Last repository change
25.10.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 25.10.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Create commit messages following Sentry conventions with conventional commits and issue references. Use when committing code changes, writing commit messages, or formatting git history with Fixes/Refs patterns.

Original author description

Create commit messages following Sentry conventions with conventional commits and issue references. Use when committing code changes, writing commit messages, or formatting git history with Fixes/Refs patterns.

How it works

  1. Format
  2. Commit Types
  3. Subject Line Checklist
  4. Body Guidelines
  5. Footer: Issue References
  6. Breaking Changes
  7. Revert Format
  8. Examples
Original SKILL.md headings · 92 lines, 308 words
SKILL.md preview
---
name: sentry-commit-messages
description: Create commit messages following Sentry conventions with conventional commits and issue references. Use when committing code changes, writing commit messages, or formatting git history with Fixes/Refs patterns.
---

# Sentry Commit Messages

## Format

```
<type>(<scope>): <subject>

<body>

<footer>
```

**Requirements:**

- Header is required; scope is optional
- All lines must stay under 100 characters
- Subject line max 70 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 Checklist

When writing the subject line:

- [ ] 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
- Wrap at 100 characters

## Footer: Issue References

Reference issues using these patterns:

```
Fixes GH-1234          # GitHub issue
Fixes #1234            # Shorthand GitHub
Fixes SENTRY-1234      # Sentry issue
Refs LINEAR-ABC-123    # Linear issue (no auto-close)
```

- `Fixes` closes the issue when merged
- `Refs` links without closing

## Breaking Changes

For breaking changes, add `!` after type/scope and include a footer:

```
feat(api)!: Remove deprecated v1 endpoints

BREAKING CHANGE: v1 endpoints no longer available
```

## Revert Format

```
revert: feat(api): Add new endpoint

This reverts commit abc123def456.

Reason: Caused performance regression in production.
```

## Examples

See [examples.md](examples.md) for detailed commit examples across different scenarios.

Versions

The database has no other skills named sentry-commit-messages.

Database snapshot: 13.11.2026 · package version 7813a2406ebe (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100commit
    Create commit messages following Sentry conventions. Use when committing code changes, writing commit messages, or formatting git history. Follows conventional commits with Sentry-specific issue references.
  • 100commit
    Create commit messages following Sentry conventions. Use when committing code changes, writing commit messages, or formatting git history. Follows conventional commits with Sentry-specific issue references.
  • 100commit
    Create commit messages following Sentry conventions. Use when committing code changes, writing commit messages, or formatting git history. Follows conventional commits with Sentry-specific issue references.
  • 100commit
    Create commit messages following Sentry conventions. Use when committing code changes, writing commit messages, or formatting git history. Follows conventional commits with Sentry-specific issue re...
  • 100conventional-commit
    Create conventional commit messages following best conventions. Use when committing code changes, writing commit messages, or formatting git history. Follows conventional commits specification.
  • 100conventional-commits
    Create conventional commit messages following best conventions. Use when committing code changes, writing commit messages, or formatting git history. Follows conventional commits specification.

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.