Sentry commit messages: conventional commits with issue references
Draft Sentry-style conventional commits — type(scope), imperative subject, footers with Fixes/Refs issue links
- What
- Draft Sentry-style conventional commits — type(scope), imperative subject, footers with Fixes/Refs issue links
- Cost
- Free
- Needs
- nothing to install — the skill is a commit-message convention your agent follows; a git repo to commit in, obviously
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
Curated by Skill Harbor — @getsentry's convention for writing commits, packaged as an agent skill. Before committing, it checks the current branch (creates a feature branch if on main/master unless told otherwise) and commits one coherent, independently reviewable change at a time. Message rules: `<type>(<scope>): <subject>` with imperative present-tense subject (capitalized, ≤70 chars, no trailing period), all lines under 100 chars, body only when useful, never any customer names, emails, secrets or PII. The type set goes beyond classic conventional commits (feat, fix, ref, perf, docs, test, build, ci, chore, style, meta, license, revert) — note `ref` for behavior-free refactoring, `style` for logic-free formatting, `meta` for repo metadata. Footers: `Fixes <issue>` to close, `Refs <issue>` to link, `BREAKING CHANGE:` for breaking changes; commit multi-paragraph messages with separate `-m` flags, never literal `\n` or an interactive editor. Honest caveats: it's a message convention, not tooling — opinionated choices (capitalized subject, `meta` type, the Sentry-specific types) may clash with your own project's commit style. Apache-2.0 licensed. Skill Harbor never reviews the code, review it yourself before use. Discovered via skills.sh.
Version:
Install
Prerequisites: nothing to install — the skill is a commit-message convention your agent follows; a git repo to commit in, obviously Install "Sentry commit messages: conventional commits with issue references" for me. It gives my agent @getsentry's commit convention: check the branch first (feature branch when on main/master unless told otherwise), one coherent change per commit, <type>(<scope>): <subject> with imperative capitalized subject (≤70 chars), lines under 100 chars, Sentry's type set (including ref, style, meta), footers Fixes/Refs <issue> and BREAKING CHANGE:, multi-paragraph messages via separate -m flags, and never any secrets or PII in messages. Apache-2.0 licensed. Repository: https://github.com/getsentry/skills/blob/main/skills/commit/SKILL.md 1. Fetch the SKILL.md file (and any helper files) from the repository path into a temporary folder and summarize what it does in one or two sentences. 2. Safety check: review the SKILL.md and scripts for anything suspicious (unexpected network calls, shell commands, credential harvesting). This repo should contain zero secrets in code, credentials only via the secure vault, allowed hosts declared in the SKILL.md. Verify that holds here; STOP on any red flag and tell me. 3. Install it as a skill: copy SKILL.md and its helper files into the agent's skills directory, in a folder named "commit". 4. Verify with no network calls: frontmatter valid, files in place. 5. Report what was installed, where, and what I still need to do myself (e.g. tell the agent which changes to commit; it drafts the message in the Sentry style). GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Never require it unless it's in the prerequisites above. Rules: don't touch anything outside the temp folder and the install target. If anything looks off, stop and ask me.
Questions
How do I install a build?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the build up for you — no manual configuration.
Where does my money go?
Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.
What does the ✓ next to a creator’s name mean?
It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a build before installing it.