사용 방법
- 설치 명령을 복사하고 자신의 에이전트 환경에 설치하기 전에 소스 패키지를 확인하세요.
- 필요한 도구, 인증 정보, 지원 환경은 원본 문서에서 확인하세요.
- 입력과 원하는 산출물을 설명하고 출처와 결과를 대조하세요.
npx skills add https://github.com/yeachan-heo/oh-my-claudecode --skill omc-review시작 전 확인
- 설치에는 모델 구독, API 한도, 파일 접근 권한이 포함되지 않습니다.
- 별점 수와 설치 수는 활동 지표이며 독립적인 품질·보안 검증이 아닙니다.
원본 Skill 문서
원본 저장소의 제목, 예시, 코드, 표, 링크, 이미지를 유지해 표시합니다.
Review
Use this skill to evaluate work that already exists. Review never authors the change it is judging.
This is the canonical review workflow. merge-readiness routes here, and ai-slop-cleaner is an opt-in lane within it.
Goal
Find what is actually wrong, ranked by severity, with enough detail to act on.
Workflow
- Establish what changed and what it was meant to do.
- Read the change against that intent.
- Check correctness first, then risk, then simplification.
- Verify each candidate finding before reporting it.
- Report findings most-severe first.
What to check
- Correctness — logic defects, edge cases, error paths, concurrency
- Risk — security boundaries, destructive operations, data integrity
- Reuse — existing utilities or patterns the change should have used
- Simplification — code that could be deleted or collapsed
- Coverage — behavior that ships untested
Rules
- Separate lanes: the reviewer must not be the author's same active context.
- Verify before reporting. A plausible-sounding finding that does not reproduce is noise.
- State severity honestly; do not pad the list to look thorough.
- "No findings" is a valid result when the work is sound.
- Advisory by default — review informs, it does not gate. Hard gates (release,
security, destructive operations) stay separate and fail closed.
Output
- Findings, most-severe first, each with file, line, and concrete failure scenario
- What was checked and found clean
- Anything that could not be assessed
