review
Skill7 starsChanged 4 months agoMITView on GitHub
Review a pull request or diff — language-aware dispatcher. Detects which file types are changed and fans out to the right specialist skills automatically. Each specialist skill runs itself as an isolated subagent and determines its own diff scope, so the review doesn't inherit the implementing session's bias and never scans the whole repo. If any must-fix findings are found, AUTO-INVOKE review-loop to apply auto-fixable corrections and re-check. Triggers include "PR 리뷰해", "코드 리뷰해", "review this", "review my PR", "리뷰해줘". Replaces the default /review skill with a smarter routing layer.
192 other projects use a version of this.
Adopted by
Most recently taken up by
- microsoft/veronatheir own version, first seen Nov 8, 2026
- microsoft/FluidFrameworktheir own version, first seen Nov 8, 2026
- charliee1w/consolidation-memorytheir own version, first seen Nov 8, 2026
- jisuzzzz/haechitheir own version, first seen Nov 8, 2026
- apokamo/kajitheir own version, first seen Nov 8, 2026
- dirien/yet-another-agent-harnesstheir own version, first seen Nov 8, 2026
Used with
Projects with it also use close-spec, design-with-images 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.
dzhngSkillclose-spec
When a spec under specs/<feature>/ is done shipping (a write-spec build, or any planned task that produced a spec), archive it to specs/done/ and rewrite it from a build-plan into a durable rationale — the why, the principles, the invariants — pointing back to the real code for the how. Use when implementation has landed and the plan no longer matches what shipped, or the user says a feature/spec is finished. Pairs with [write-spec](../write-spec/SKILL.md) (the plan this closes) and [review](../review/SKILL.md) (run before closing).
Also in 5 projects that use this
dzhngSkilldesign-with-images
Explore UI and visual design with image generation, then iterate the real implementation against the user-selected concept. Use when brainstorming visual directions, offering mockup variants, or implementing an approved generated design; do not stop at the mockups or the first code approximation.
Also in 5 projects that use this
LambenthanSkilldaily-arxiv
每日从 arXiv 拉取新论文,过滤相关性,auto-ingest 高优先级论文,检测 SOTA 更新
Also in 5 projects that use this
LambenthanSkillexp-eval
实验判决门:Review LLM 独立评判实验结果 → 4 种判决路径 → 自动更新 claims confidence、ideas status、graph edges
Also in 5 projects that use this
- +3 more from dzhng
- +5 more from Lambenthan
Other versions192 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 192
- garrytan/gstack★ 141ksame name
- ansible/ansible★ 71ksame name
- docling-project/docling★ 70ksame name
- traefik/traefik★ 65ksame name
- ClickHouse/ClickHouse★ 51ksame name
- temporalio/temporal★ 24ksame name
- tisfeng/Easydict★ 15ksame name
- juicedata/juicefs★ 15ksame name
- elie222/inbox-zero★ 13ksame name
- gitkraken/vscode-gitlens★ 10ksame name
182 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 repository14 other files it gives its agents.
- ai-tell-cleanupSkill
- branch-guardSkill
- frontend-perf-impact-scanSkill
- jvm-memory-leak-reviewSkill
- kotlin-coroutine-reviewSkill
- nestjs-provider-reviewSkill
- nextjs-app-router-reviewSkill
- parallel-devSkill
- parallel-dispatchSkill
- parallel-prSkill
- pr-impact-scanSkill
- react-hooks-reviewSkill
- review-loopSkill
- spring-kafka-listener-reviewSkill
The file
Files
review — language-aware PR review dispatcher
PR 리뷰를 요청하면 diff를 스캔해서 변경된 언어/프레임워크에 맞는 전문 스킬을 자동으로 실행합니다.
사용자는 /review 하나만 알면 됩니다.
Phase 1 — Enumerate changed files
현재 브랜치와 base 브랜치 사이의 diff를 수집합니다:
git diff --name-only $(git merge-base HEAD main)...HEADbase 브랜치가 main이 아닐 수 있으므로 확인:
git remote show origin | grep "HEAD branch"
gh pr view --json baseRefName -q .baseRefName 2>/dev/null파일 목록을 언어별로 분류합니다:
| 언어/프레임워크 | 패턴 |
| Java | *.java |
| Kotlin | *.kt, *.kts |
| TypeScript/React | *.tsx, *.jsx |
| TypeScript/NestJS | *.ts in src/ with @Module, @Controller, @Injectable |
| Next.js | *.tsx under app/ or pages/ |
Phase 2 — Run general PR review
모든 언어에 공통으로 먼저 일반 PR 리뷰를 수행합니다:
- PR title, description, scope 확인
- diff 크기 및 의도 파악
- 명백한 로직 오류, 하드코딩된 값, 보안 이슈 (SQL injection, XSS, secret 노출) 체크
- 테스트 커버리지 갭 확인
Phase 3 — Language-specific dispatch (subagent)
Phase 1에서 감지된 파일 타입에 따라 아래 스킬을 Skill 도구로 호출합니다. 복수의 언어가 감지되면 모두 병렬로 호출합니다.
Java / Kotlin 파일이 있는 경우 → jvm-memory-leak-review
.java 또는 .kt 파일이 diff에 포함되면 반드시 실행:
- Static 컬렉션 누적 패턴
- ThreadLocal remove() 누락
- Listener unregister 누락
- 무한 캐시 (TTL/크기 제한 없음)
- 미닫힌 리소스 (Stream, Connection, EntityManager)
- Bean scope 불일치 (singleton이 prototype 직접 주입)
- @Async / CompletableFuture 대형 객체 캡처
Kotlin 파일이 있는 경우 → kotlin-coroutine-review
.kt 파일이 포함되면 실행:
- blocking call in suspend function
- GlobalScope / structured-concurrency 위반
- Dispatcher 오용 (IO vs Default)
- CoroutineExceptionHandler 누락
- Flow / Channel 백프레셔 문제
Kafka listener가 있는 경우 → spring-kafka-listener-review
@KafkaListener 어노테이션이 diff에 포함되면 실행:
git diff $(git merge-base HEAD main)...HEAD | grep -l "@KafkaListener"React/Next.js 파일이 있는 경우 → react-hooks-review
.tsx / .jsx 파일이 포함되면 실행:
- useEffect dependency array 오류
- stale closure
- async effect cleanup 누락
NestJS 파일이 있는 경우 → nestjs-provider-review
.ts 파일에서 @Injectable, @Module, @Controller 가 포함되면 실행.
Phase 4 — Aggregate findings
각 subagent(forked skill)의 결과를 하나의 리포트로 합칩니다:
## PR Review — <브랜치명>
### General
<공통 리뷰 결과>
### JVM Memory Leak (jvm-memory-leak-review)
<findings or "발견 없음">
### Kotlin Coroutines (kotlin-coroutine-review)
<findings or "해당 없음 — Kotlin 파일 없음">
...must-fix 항목이 하나라도 있으면 리포트 상단에 강조합니다.
발견이 전혀 없으면 "전 항목 통과 — PR 머지 준비됨" 으로 명시합니다.
Non-goals
- 이 스킬은 직접 코드를 수정하지 않습니다.
- PR을 자동으로 열거나 닫지 않습니다.
- 비즈니스 로직의 정확성 판단은 이 스킬 범위 밖입니다.
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.

