AI TOOLS RADAR
모든 Skills / ZHONGSHIXI
zhongshixi/agent-skills

pull-request-code-review

Review a GitHub pull request or a GitLab merge request for correctness, missing tests, and security issues in the diff.

소스 보기

사용 방법

  1. 설치 명령을 복사하고 자신의 에이전트 환경에 설치하기 전에 소스 패키지를 확인하세요.
  2. 필요한 도구, 인증 정보, 지원 환경은 원본 문서에서 확인하세요.
  3. 입력과 원하는 산출물을 설명하고 출처와 결과를 대조하세요.
npx skills add https://github.com/zhongshixi/agent-skills --skill pull-request-code-review

시작 전 확인

  • 설치에는 모델 구독, API 한도, 파일 접근 권한이 포함되지 않습니다.
  • 별점 수와 설치 수는 활동 지표이며 독립적인 품질·보안 검증이 아닙니다.
원본 Skill 문서

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

Review Steps

1. Confirm the reviewer

If the user is not an assigned reviewer, ask whether to continue. Review only an open pull request or merge request.

2. Prepare the review

  1. On GitHub, use gh pr diff and gh pr view when the pull request number is known. On GitLab, use glab mr diff and glab mr view when the merge request number is known.
  2. The working directory must be the target repository. If it is not, ask the user to clone it.
  3. Update the local base branch and head branch.
  4. Skip the review when this skill already reviewed the current head commit. Review again when that commit has changed.
  5. Read changed files and the code they call or that calls them. Leave the rest of the repository unread.
  6. Do not modify code.
  7. Do not open credential or secret files.

3. Verify the changed behavior

When the pull request or merge request states its intent, find where the change misses that intent: a stated case left unhandled, or behavior that contradicts the intent. Trace the new path for wrong results, dropped errors, and broken callers. Follow a call outside the diff when the diff can trigger a bug there.

4. Classify review effort

High-risk items

Crashes, exceptions, memory leaks, races, deadlocks, cache corruption, missing retries, missing authentication or permissions, breaking changes to contracts other modules depend on, and code that does not build.

Medium-risk items

Mistakes in feature or bug-fix logic.

Low-risk items

Mechanical changes: renames, formatting, documentation, comments, version bumps, test-only changes, generated code, config values with no logic, and indentation. Treat indentation as high-risk in languages where indentation is syntax, such as Python.

5. Check the tests

Point to a test that fails when the change is reverted, or report the missing test.

6. Write the review comment

Post the comment as the authenticated GitHub or GitLab user. For each finding:

  1. risk-level: high, medium, or low
  2. description: the issue and its category
  3. reason: why it is an issue, and the scenario that triggers it
  4. suggestion: one or more fixes

End the comment with the name of the model that produced the review.

7. Approve the Pull Request

If all high-risk items and medium-risk items are not found or they are addressed by follow-up commits, approve the pull request