跳到主内容
智客 ZICQ

技能库 智客分类:Agent 工作流 sentry-pr-code-review

Sentry Pr Code Review

审查一个项目的PR,检查Seer Bug Pregency在代码审查中发现的问题. 被请求时用于审查或解决哨兵在公关评论中发现的问题,或找到有哨兵反馈的近期公关.

604 安装量

官方网址:skills.sh

技能介绍

先看中文介绍;官方 description 原文单独保留,不改写 SKILL.md。

做什么

检查项目的 PR , 检查 Seer Bug 预测在代码审查中发现的问题

何时用

要求审查或解决哨兵公司在公关评论中发现的问题,或根据哨兵公司的反馈找到最近的公关

代理如何加载

按 Agent Skills 渐进披露:启动时只加载 name 与 description(约 100 token);任务匹配后才读入整份 SKILL.md 正文;scripts/、references/、assets/ 仅在需要时再读。 本文件正文结构:Sentry Code Review、Invoke This Skill When、Prerequisites、Phase 1: Fetch Seer Comments、Phase 2: Parse Each Comment、Phase 3: Verify & Fix。

文件分析

文件分析:这是一份仅含 SKILL.md 的指令型技能,代理激活后整份正文进入上下文。

官方 description(原文)

Review a project's PRs to check for issues detected in code review by Seer Bug Prediction. Use when asked to review or fix issues identified by Sentry in PR comments, or to find recent PRs with Sentry feedback.

Sentry Code ReviewInvoke This Skill WhenPrerequisitesPhase 1: Fetch Seer CommentsPhase 2: Parse Each CommentPhase 3: Verify & FixPhase 4: Summarize and Report ResultsSeer Review: PR #[number]ResolvedSkipped (false positive or already fixed)Seer Review TriggersTroubleshooting

· 许可:Apache-2.0

来源分类:skills.sh agent-skill

SKILL.md 与 Agent 调用

官方规范 ↗
name
sentry-pr-code-review
description
Review a project's PRs to check for issues detected in code review by Seer Bug Prediction. Use when asked to review or fix issues identified by Sentry in PR comments, or to find recent PRs with Sentry feedback.
许可
Apache-2.0
  1. 发现技能客户端向 Agent 提供名称与描述目录。
  2. 匹配与调用用户指定或任务匹配后,载入 SKILL.md 指令。
  3. 按需加载按步骤读取参考文档、使用脚本与素材。

具体调用语法与可用工具以目标 Agent 客户端为准。 查看调用机制说明 ↗

安装这个技能

Skills CLI ↗

先选择目标 Agent 和安装范围,保留技能包的附属文件,安装后检查客户端能否发现该技能。

交给 Agent 安装

复制安装指令给支持 Agent Skills 的代理,确认其中的目标目录与客户端匹配。

把 Agent Skill「sentry-pr-code-review」安装到我的项目:SKILL.md 原文与官方 description 见 https://zicq.com/zh/skills/skl-6f4548b2b93b4ca8-%E5%93%A8%E5%85%B5Pr-%E7%A0%81%E6%A3%80%E8%AE%A8.html
请存为 .cursor/skills/sentry-pr-code-review/SKILL.md 或 .claude/skills/sentry-pr-code-review/SKILL.md,frontmatter 的 name 与 description 保持原样,不要改写。

GitHub 完整包 ↗

终端安装 · Skills CLI

需要 Node.js 与 npx。先查看仓库技能列表,确认实际名称。

npx skills add 'https://github.com/getsentry/sentry-agent-skills' --list

npx skills add 'https://github.com/getsentry/sentry-agent-skills' --skill 'sentry-pr-code-review'

CLI 会交互选择目标 Agent,默认安装到项目;用户级安装使用 -g。先通过查看命令核对仓库内容,再用 npx skills list 检查已安装技能。

阅读排版
--- name: sentry-pr-code-review description: Review a project's PRs to check for issues detected in code review by Seer Bug Prediction. Use when asked to review or fix issues identified by Sentry in PR comments, or to find recent PRs with Sentry feedback. license: Apache-2.0 --- # Sentry Code Review Review and fix issues identified by Seer (by Sentry) in GitHub PR comments. ## Invoke This Skill When - User asks to "review Sentry comments" or "fix Sentry issues" on a PR - User shares a PR URL/number and mentions Sentry or Seer feedback - User asks to "address Sentry review" or "resolve Sentry findings" - User wants to find PRs with unresolved Sentry comments ## Prerequisites - `gh` CLI installed and authenticated - Repository has the [Seer by Sentry](https://github.com/apps/seer-by-sentry) GitHub App installed **Important:** The comment format parsed below is based on Seer's current output. This is not an API contract and may change. Always verify the actual comment structure. ## Phase 1: Fetch Seer Comments ```bash gh api repos/{owner}/{repo}/pulls/{PR_NUMBER}/comments --paginate \ --jq '.[] | select(.user.login == "seer-by-sentry[bot]") | {file: .path, line: .line, body: .body}' ``` **The bot login is `seer-by-sentry[bot]`** — not `sentry[bot]` or `sentry-io[bot]`. If no PR number is given, find recent PRs with Seer comments: ```bash gh pr list --state open --json number,title --limit 20 | \ jq -r '.[].number' | while read pr; do count=$(gh api "repos/{owner}/{repo}/pulls/$pr/comments" --paginate \ --jq '[.[] | select(.user.login == "seer-by-sentry[bot]")] | length') [ "$count" -gt 0 ] && echo "PR #$pr: $count Seer comments" done ``` ## Phase 2: Parse Each Comment Extract from the markdown body: - **Bug description**: Line starting with `**Bug:**` - **Severity/Confidence**: In `Severity: X | Confidence: X.XX` - **Analysis**: Inside `🔍 Detailed Analysis` block - **Suggested Fix**: Inside `💡 Suggested Fix` block - **AI Prompt**: Inside `🤖 Prompt for AI Agent` block ## Phase 3: Verify & Fix For each issue: 1. Read the file at the specified line 2. Confirm issue still exists in current code (not already fixed in a later commit) 3. Review surrounding code to assess if it's an actual issue or false positive 4. Implement fix (use suggested fix as starting point, or write your own) 5. Consider edge cases and regression risk ## Phase 4: Summarize and Report Results ```markdown ## Seer Review: PR #[number] ### Resolved | File:Line | Issue | Severity | Fix Applied | |-----------|-------|----------|-------------| | path:123 | desc | HIGH | what done | ### Skipped (false positive or already fixed) | File:Line | Issue | Reason | |-----------|-------|--------| **Summary:** X resolved, Y skipped ``` ## Seer Review Triggers | Trigger | When | |---------|------| | PR set to "Ready for Review" | Automatic error prediction | | Commit pushed while PR is ready | Re-runs prediction | | `@sentry review` comment | Manual trigger for full review + suggestions | | Draft PR | Skipped — no review until marked ready | ## Troubleshooting | Issue | Solution | |-------|----------| | No Seer comments found | Verify the Seer GitHub App is installed on the repo | | Bot name mismatch | The login is `seer-by-sentry[bot]`, not `sentry[bot]` | | Comments not appearing on new PRs | PR must be "Ready for Review" (not draft) | | `gh api` returns partial results | Ensure `--paginate` flag is included | ## Common Issue Types | Category | Examples | |----------|----------| | Type Safety | Missing null checks, unsafe type assertions | | Error Handling | Swallowed errors, missing boundaries | | Validation | Permissive inputs, missing sanitization | | Config | Missing env vars, incorrect paths |

相关技能

Agent 工作流

Skill Creator

创造有效技能指南。 当用户想创造出新的技能(或更新现有的技能),以专业知识,工作流程,或工具集成来扩展克洛德的能力时,应该使用这种技能.

Agent 工作流

Clawdhub

使用ClawdHub CLI搜索,安装,更新并发布从taladhub.com的代理技能. 需要获取苍蝇上的新技能时使用,将安装的技能同步到最新版本或特定版本,或者发布 npm-instainddhub CLI 的新/更新的技能文件夹.

Agent 工作流

Agent Team Orchestration

管弦乐团多代理团队,任务设定周期,交接协议,审查工作流程. 使用时间: (1)建立2+特派员队伍,具有不同专业,(2)确定任务路线和生命周期(收录框_ spec_建设_审查_完成),(3)在特派员之间制定交接协议,(4)建立审查和质量关口,(5)管理特派员之间的交流和文物共享.

Agent 工作流

Superpowers

Spec-first,TDD,子代理驱动的软件开发工作流程. 当:(1)构建任何新功能或应用——触发脑暴_计划_子代理执行回路,(2)调试出一个bug或测试失败——触发系统性的根起过程,(3)用户说"让我们构建","帮助我计划","我想添加X",或"这个被打破",(4)完成一个功…