review-pr
Skill1 starsChanged 9 months agoMITView on GitHub
Review a pull request and provide feedback
185 other projects use a version of this.
Adopted by
Most recently taken up by
- torrust/torrust-trackertheir own version, first seen Nov 16, 2026
- Wendor/teapod-streamtheir own version, first seen Nov 16, 2026
- testcontainers/testcontainers-javatheir own version, first seen Nov 16, 2026
- hotcodepush-team/skillstheir own version, first seen Nov 16, 2026
- chuckplayer/claude-agent-packtheir own version, first seen Nov 16, 2026
- ayoubben18/ab-methodtheir own version, first seen Nov 15, 2026
Used with
Projects with it also use diagnose-ci-failures, review-delta and 10 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
zerx-labSkilldiagnose-ci-failures
Diagnose CI failures for a PR using the GitHub CLI, extract error logs, and generate a plan to fix them. Use when the user asks to check CI status, pull CI issues, triage test failures, or investigate PR build failures.
Also in 3 projects that use this
n24q02mSkillreview-delta
Review only changes since last commit using impact analysis. Token-efficient delta review with automatic blast-radius detection.
Also in 3 projects that use this
GeiserXSkilldocs-loop
Use when the user asks to audit docs, check documentation for stale claims, or verify docs against the code.
Also in 3 projects that use this
GeiserXSkillfull-loop
Drive a repository to done with sergio-loop, then keep improving it with refine-loop at a descending theta. Use only when the user explicitly invokes full-loop.
Also in 3 projects that use this
n24q02mSkillbuild-graph
Build or update the code review knowledge graph. Run this first to initialize, or let hooks keep it updated automatically.
Also in 3 projects that use this
- +7 more from GeiserX
Other versions185 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 185
- denoland/deno★ 109ksame name
- ToolJet/ToolJet★ 41ksame name
- remix-run/remix★ 33ksame name
- tirth8205/code-review-graph★ 33ksame name
- alpinejs/alpine★ 32ksame name
- nrwl/nx★ 29ksame name
- PrefectHQ/fastmcp★ 29ksame name
- jlowin/fastmcp★ 29ksame name
- livewire/livewire★ 24ksame name
- microsoft/fluentui★ 20ksame name
175 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository10 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- clean-worktreesSkill
- commitSkill
- create-issueSkill
- plan-issueSkill
- prSkill
- pushSkill
- review-codeSkill
- shipSkill
- start-issueSkill
The file
Files
PR 리뷰
Current State
- PR details: !
gh pr view $ARGUMENTS 2>/dev/null || echo "PR 번호를 입력해주세요" - PR diff stat: !
gh pr diff $ARGUMENTS --stat 2>/dev/null || echo "PR 번호를 입력해주세요"
Instructions
PR 번호를 입력받아 변경 사항을 분석하고 리뷰 결과를 제공한다.
1. PR 정보 수집
$ARGUMENTS가 비어 있으면 사용자에게 PR 번호를 질문한다- 위에 주입된 PR details와 diff stat으로 개요를 파악한다
- Bash로
gh pr diff <PR번호>실행하여 상세 diff를 수집한다 (동적 주입 X — 토큰 절약) - Bash로
gh pr view <PR번호> --comments를 실행하여 기존 코멘트도 확인한다
2. 리뷰 수행
리뷰 기준은 .claude/skills/shared/review-criteria.md를 따른다.
해당 파일을 Read로 읽은 뒤 공통 기준에 따라 리뷰를 수행한다.
해당 파일이 존재하지 않을 경우, 아래 인라인 기준을 사용한다:
- 코드 품질: 가독성, 중복 제거, 네이밍, 함수/모듈 분리
- 버그 가능성: 엣지 케이스, off-by-one, null/undefined 처리
- 보안 이슈: 인젝션, 하드코딩된 시크릿, 권한 검증 누락
- 컨벤션 준수: 프로젝트 코딩 스타일, lint 규칙, 포맷팅
- 테스트: 변경 사항에 대한 테스트 존재 여부 및 커버리지
추가로 PR 전용 기준을 적용한다:
- PR 설명-코드 일치: PR 본문의 설명이 실제 변경 내용과 일치하는지 확인
- PR 템플릿 체크리스트: PR 템플릿의 체크리스트 항목이 충족되었는지 확인
- 커밋 메시지 컨벤션: Conventional Commits 규칙 준수 여부 확인
3. 결과 출력
아래 형식으로 출력한다:
## PR 리뷰 결과
### PR 개요
- 제목: {PR 제목}
- 변경 파일: N개
- 커밋: N개
### 요약
- 코드 이슈: 🔴 0 / 🟡 0 / 🔵 0
- PR 설명-코드 일치: ✅ / ❌
- 템플릿 체크리스트: ✅ / ❌
- 커밋 컨벤션: ✅ / ❌
### 상세
#### 🟡 `src/main.rs:42` — 에러 처리 누락
...4. PR 코멘트 게시 (선택)
- AskUserQuestion으로 리뷰 결과를 PR 코멘트로 게시할지 질문한다:
{ "questions": [{ "question": "리뷰 결과를 PR 코멘트로 게시할까요?", "header": "코멘트 게시", "options": [ {"label": "게시", "description": "PR에 리뷰 코멘트를 게시"}, {"label": "건너뛰기", "description": "터미널 출력만으로 종료"} ], "multiSelect": false }] } - "게시" 선택 시
gh pr review <PR번호> --comment --body "<리뷰 결과>"로 게시한다 - "건너뛰기" 선택 시 터미널 출력만으로 종료한다
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

