agentleFS
zfoggzfogg/ascii-chat/.cursor/skills/sentry-commit-messages/SKILL.md

sentry-commit-messages

Skill203 starsChanged 8 days agoMITView on GitHub

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.

The file

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 3 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    All lines must stay under 100 characters

    line 21
  2. Distinctive:

    When writing the subject line:

    line 43
  3. Distinctive:

    Use imperative mood and present tense

    line 54

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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

TypePurpose
featNew feature
fixBug fix
refRefactoring (no behavior change)
perfPerformance improvement
docsDocumentation only
testTest additions or corrections
buildBuild system or dependencies
ciCI configuration
choreMaintenance tasks
styleCode formatting (no logic change)
metaRepository metadata
licenseLicense 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 for detailed commit examples across different scenarios.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.