npx skills add https://github.com/getsentry/skills --skill commit为 Sentry 项目创建提交时，请遵循以下约定。
提交前，请务必检查当前分支：
git branch --show-current
如果您当前在 main 或 master 分支上，您必须先创建一个功能分支 —— 除非用户明确要求提交到 main 分支。不要询问用户是否创建分支；直接进行分支创建。create-branch 技能应自动推导并创建一个合适的分支名称。
使用 create-branch 技能来创建分支。在 create-branch 完成后，继续操作前请验证当前分支是否已更改：
git branch --show-current
如果仍然在 main 或 分支上，请停止操作 —— 不要提交。
广告位招租
在这里展示您的产品或服务
触达数万 AI 开发者，精准高效
master<类型>(<范围>): <主题>
<正文>
<页脚>
头部是必需的。范围是可选的。所有行必须保持在 100 个字符以内。
| 类型 | 用途 |
|---|---|
feat | 新功能 |
fix | 错误修复 |
ref | 重构（无行为变更） |
perf | 性能改进 |
docs | 仅文档 |
test | 测试添加或修正 |
build | 构建系统或依赖项 |
ci | CI 配置 |
chore | 维护任务 |
style | 代码格式化（无逻辑变更） |
meta | 仓库元数据 |
license | 许可证变更 |
\n 序列从 CLI 创建提交时，不要在 -m 字符串内嵌入转义的换行符，如 \n。这会在最终的提交消息中产生字面的反斜杠字符。
优先使用以下模式之一：
git commit -m "type(scope): Subject" \
-m "First paragraph with real line wrapping.
Second paragraph.
Fixes GH-1234
Co-Authored-By: (the agent's name and attribution byline)"
git commit
当消息需要仔细格式化时，请使用编辑器流程。
使用以下模式在页脚中引用问题：
Fixes GH-1234
Fixes #1234
Fixes SENTRY-1234
Refs LINEAR-ABC-123
Fixes 在合并时关闭问题Refs 仅链接而不关闭当变更主要由编码代理生成时，请在提交页脚中包含 Co-Authored-By 署名。代理应使用其自身身份：
Co-Authored-By: (the agent's name and attribution byline)
示例：Co-Authored-By: Claude Sonnet 4 <noreply@example.com>
这是提交中应出现的唯一 AI 参与指示。不要在主题、正文或提交消息的任何其他地方添加诸如 "Generated by AI"、"Written with Claude" 或类似标记的短语。
fix(api): 处理用户端点中的空响应
用户 API 可能为已删除的账户返回 null，导致仪表板崩溃。在访问用户属性前添加空值检查。
Fixes SENTRY-5678
Co-Authored-By: (the agent's name and attribution byline)
feat(alerts): 为警报更新添加 Slack 线程回复
当警报被更新或解决时，回复到原始的 Slack 线程，而不是创建新消息。这使相关通知保持分组。
Refs GH-1234
ref: 将通用验证逻辑提取到共享模块
将三个端点中的重复验证代码移动到共享验证器类中。无行为变更。
feat(api)!: 移除已弃用的 v1 端点
移除在 23.1 版本中已弃用的所有 v1 API 端点。客户端应迁移到 v2 端点。
BREAKING CHANGE: v1 端点不再可用
Fixes SENTRY-9999
revert: feat(api): 添加新端点
This reverts commit abc123def456.
原因：导致生产环境性能回归。
每周安装量
360
仓库
GitHub 星标数
454
首次出现
2026 年 1 月 20 日
安全审计
安装于
opencode312
codex307
gemini-cli304
github-copilot297
claude-code283
cursor278
Follow these conventions when creating commits for Sentry projects.
Before committing, always check the current branch:
git branch --show-current
If you're onmain or master, you MUST create a feature branch first — unless the user explicitly asked to commit to main. Do not ask the user whether to create a branch; just proceed with branch creation. The create-branch skill should derive and create a suitable branch name automatically.
Use the create-branch skill to create the branch. After create-branch completes, verify the current branch has changed before proceeding:
git branch --show-current
If still on main or master, stop — do not commit.
<type>(<scope>): <subject>
<body>
<footer>
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 |
\n sequencesWhen creating commits from the CLI, do not embed escaped newlines like \n inside -m strings. That produces literal backslash characters in the final commit message.
Prefer one of these patterns:
git commit -m "type(scope): Subject" \
-m "First paragraph with real line wrapping.
Second paragraph.
Fixes GH-1234
Co-Authored-By: (the agent's name and attribution byline)"
git commit
Use the editor flow when the message needs careful formatting.
Reference issues in the footer using these patterns:
Fixes GH-1234
Fixes #1234
Fixes SENTRY-1234
Refs LINEAR-ABC-123
Fixes closes the issue when mergedRefs links without closingWhen changes were primarily generated by a coding agent, include the Co-Authored-By attribution in the commit footer. Agents should use their own identity:
Co-Authored-By: (the agent's name and attribution byline)
Example: Co-Authored-By: Claude Sonnet 4 <noreply@example.com>
This is the only indicator of AI involvement that should appear in commits. Do not add phrases like "Generated by AI", "Written with Claude", or similar markers in the subject, body, or anywhere else in the commit message.
fix(api): Handle null response in user endpoint
The user API could return null for deleted accounts, causing a crash
in the dashboard. Add null check before accessing user properties.
Fixes SENTRY-5678
Co-Authored-By: (the agent's name and attribution byline)
feat(alerts): Add Slack thread replies for alert updates
When an alert is updated or resolved, post a reply to the original
Slack thread instead of creating a new message. This keeps related
notifications grouped together.
Refs GH-1234
ref: Extract common validation logic to shared module
Move duplicate validation code from three endpoints into a shared
validator class. No behavior change.
feat(api)!: Remove deprecated v1 endpoints
Remove all v1 API endpoints that were deprecated in version 23.1.
Clients should migrate to v2 endpoints.
BREAKING CHANGE: v1 endpoints no longer available
Fixes SENTRY-9999
revert: feat(api): Add new endpoint
This reverts commit abc123def456.
Reason: Caused performance regression in production.
Weekly Installs
360
Repository
GitHub Stars
454
First Seen
Jan 20, 2026
Security Audits
Gen Agent Trust HubPassSocketPassSnykPass
Installed on
opencode312
codex307
gemini-cli304
github-copilot297
claude-code283
cursor278
React 组合模式指南：Vercel 组件架构最佳实践，提升代码可维护性
106,200 周安装
build| Build system or dependencies |
ci | CI configuration |
chore | Maintenance tasks |
style | Code formatting (no logic change) |
meta | Repository metadata |
license | License changes |