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 한도, 파일 접근 권한이 포함되지 않습니다.
  • 별점 수와 설치 수는 활동 지표이며 독립적인 품질·보안 검증이 아닙니다.
원본 Skill 문서

원본 저장소의 제목, 예시, 코드, 표, 링크, 이미지를 유지해 표시합니다.

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.