Enforce conventional commit formats and branch hygiene across Sentry projects.
npx skills add https://github.com/getsentry/skills --skill commit-getsentry
Please help me install this Agent Skill. Skill: commit Source: https://github.com/getsentry/skills/tree/main/skills/commit Command: npx skills add https://github.com/getsentry/skills --skill commit-getsentry
Improper or inconsistent commit messages hinder traceability and project hygiene. This Skill enforces Sentry's conventional commit standards, guiding developers to craft clear subject lines, include necessary references, and apply proper branching practices.
Begin committing with standardized messages by activating the commit skill and following the on-screen prompts.
High-intent search queries and answers about installing and using this skill.
To enforce conventional commit messages, this Skill validates allowed commit types like feat, fix, and perf, checks subject lines stay under 70 characters, and verifies footer references like Fixes GH-1234.
Preventing direct commits to main or master requires guardrails that block pushes to protected branches and coordinate with create-branch workflows to establish a feature branch before committing.
Allowed conventional commit types for version control include feat, fix, ref, perf, docs, test, build, ci, chore, style, and meta, ensuring categorization aligns with project standards.
Attributing AI-generated commits involves appending a Co-Authored-By footer to the commit message, ensuring automated authorship handling follows defined conventions and traceability standards.
Validating footer references like issue numbers is supported by checking that commit messages include properly formatted entries such as Fixes GH-1234 to maintain traceability and project hygiene.
Standardizing branch hygiene and commit formats is best achieved by applying automated guardrails during the commit process, verifying branch creation, post-branch state, and message conventions across all projects.
NagyViktStage, commit, and push verified changes to non-default Git branches with conventional messages.
fabiolpgomesEnforce quality gates and orchestrate GitHub releases with semantic versioning.
imvanzenCreate and switch to a new branch from the repository default branch.
eysenfalkEnforce Git branch naming, commit message formats, and merge policies.
