ammuench/ammuench_skills

review-guide

Review a pull request or branch diff for bugs, risks, and gaps, and provide a concise walkthrough guide for engineer triage.

查看源码

使用方法

  1. 复制安装命令,在自己的智能体环境安装前先检查源码包。
  2. 从原始文档核对所需工具、凭据和支持的宿主。
  3. 说明输入材料与期望交付物,并对照来源检查输出。
npx skills add https://github.com/ammuench/ammuench_skills --skill review-guide

开始前需了解

  • 安装不包含模型订阅、API 额度或访问文件的权限。
  • 仓库星数和安装量反映活跃情况,不等于独立质量或安全测试。
仓库原始内容

按源仓库内容呈现,保留标题、案例、代码、表格、链接以及原文引用的演示图片。

review-guide

When to use

Use when the user asks for a code review of a remote pull request link or local branch changes versus the default branch.

Instructions

  1. Get the diff:
  • If PR link provided: fetch remote diff + existing PR comments. If fetch fails (auth, network, bad link), STOP and ask user to unblock.
  • If no link: diff current branch against default branch (usually main, sometimes develop or master). Ask if unclear.
  1. If the PR references a ticket (Jira, Linear, GitHub issue), fetch it for context. If none, proceed.
  2. Review only changed lines plus direct impacts. For each finding, give filepath:line_number. Use Conventional Comments format (see https://conventionalcomments.org/): labels praise:, nitpick:, suggestion:, issue:, question: with decorations (blocking), (non-blocking), (if-minor) to signal merge impact. Cover bugs, logic, architecture, testing gaps, AC mismatch, security, and so on.
  3. Verdict: Approve = non-blocking comments only. Comment = needs clarification but don't block for churn. Request Changes = blocking bug or harmful pattern. When in doubt, favor Request Changes.
  4. Provide a guide: group related files in logical read order (feature before tests), explain what each group does and what to focus on.
  5. Render both artifacts directly in chat concisely: short sentences, bullets/lists, ASD-STE100 plain language. No paragraphs unless necessary. Do not create files unless the user explicitly requests file output.