SKILL

commit

按照 Sentry 约定创建提交信息。在提交代码更改、编写提交信息或格式化 git 历史时使用。遵循常规提交规范并引用 Sentry 特定议题。

机器翻译

查看英文原文

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.

适用对象：软件开发与测试。自动收录 · 待核查。

原作者说明节选

从固定版本的 SKILL.md 提取，保留原文语言。以下内容属于作者说明，本站尚未验证安装、兼容或运行结果。

查看英文原文

原文涵盖的主题

Sentry Commit Messages
Format
Commit Types
Subject Line Rules
Body Guidelines
Footer: Issue References
Examples
Simple fix

Follow these conventions when creating commits for Sentry projects. The header is required. Scope is optional. All lines must stay under 100 characters. | 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 | Use imperative, present tense: "Add feature" not "Added feature" Capitalize the first letter No period at the end Maximum 70 characters Explain what and why, not how Use imperative mood and present tense Include motivation for the change Contrast with previous behavior when relevant Reference issues in the footer using these patterns: Fixes closes the issue when merged Refs links without closing Each commit should be a single, stable change Commits should be independently reviewable The repository should be in a working state after each commit Sentry Commit Messages

来源仓库: davila7/claude-code-templates
源文件: cli-tool/components/skills/sentry/commit/SKILL.md
固定版本: 21be197f100a12b8d0dd9a211cc244c8179f84d3

阅读完整原作者说明 ↗