skills.rest
bcastelino
bcastelinoCOMMUNITY
Explore all skills by this author →
Website𝕏@cas7elinoGitHub

commit

Generate conventional commit messages with Sentry issue references.

2|Updated Feb 6, 2026
Search Tags:#git#code review#version control#conventional commits#commit message#sentry
One-click install
npx skills add https://github.com/bcastelino/agent-skills-kit --skill commit-bcastelino
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: commit
Source: https://github.com/bcastelino/agent-skills-kit/tree/main/skills/commit
Command: npx skills add https://github.com/bcastelino/agent-skills-kit --skill commit-bcastelino

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps developers consistently create well-formatted commit messages that adhere to Sentry's conventions, improving code history clarity and issue tracking.

Core Features & Use Cases

  • Conventional Commits: Enforces a structured format for commit messages (type, scope, subject, body, footer).
  • Sentry Issue Linking: Facilitates referencing Sentry issues directly within commit footers.
  • AI Co-Authorship: Standardizes attribution for AI-generated code contributions.
  • Use Case: When you've fixed a bug related to Sentry issue SENTRY-1234, use this skill to generate a commit message like fix(api): Resolve null pointer in user lookup. Fixes SENTRY-1234.

Quick Start

Use the commit skill to generate a commit message for a new feature that fixes Sentry issue SENTRY-5678.

Frequently Asked Questions about commit

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I write a conventional commit message that links a Sentry issue?▼

To generate a conventional commit message linking a Sentry issue, use a structured format with a type, scope, subject, and footer referencing the issue ID, such as `fix(api): Resolve bug. Fixes SENTRY-1234`.

What commit types are supported for Sentry-style conventional commits?▼

Sentry-style conventional commits support various types including feat, fix, ref, perf, docs, test, build, ci, chore, style, meta, license, and revert to categorize code changes accurately.

How do I format AI co-authorship attributions in a commit message?▼

AI co-authorship attributions in commit messages are formatted in the footer to standardize credit for AI-generated code contributions, ensuring clear tracking of human and AI collaboration.

When do I need a structured commit header, body, and footer?▼

You need a structured commit header, body, and footer when adhering to Sentry's conventional commit standards, which improves code history clarity, facilitates issue tracking, and structures complex changes.

Does this commit message generator work without external dependencies?▼

Yes, this commit message generator operates without external dependencies, allowing you to create structured commit messages adhering to Sentry's conventions directly within your development workflow.

Related Skills

Explore More Software Engineering Skills→
ANcpLuaANcpLua
5

smart-commit

Generate conventional commit messages from staged changes with type, scope, and issue references.

Community
Basic
ThedouglerThedougler

git-commit

Generate conventional git commit messages with automated file staging.

Community
Intermediate
first-flukefirst-fluke
1

scm

Automate Git branching, merging, and conflict management workflows.

Official
Intermediate
vulikjulikvulikjulik

aif-commit

Generate conventional commit messages from staged git changes.

Community
Intermediate