Complete code review workflow for both requesting and receiving reviews. Use when creating PRs, reviewing code, or responding to feedback.
Scanned 9/3/2026
Install to Claude Code
npx -y skills add aiskillstore/marketplace --skill code-review --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Code Review?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/aiskillstore-code-review-af9ab520)More formats (shields.io, HTML) on the badges page.
---
name: code-review
description: Complete code review workflow for both requesting and receiving reviews. Use when creating PRs, reviewing code, or responding to feedback.
allowed-tools: Read, Glob, Grep, Edit, Write, Bash
license: MIT
metadata:
author: obra/superpowers
version: "2.0"
---
# Code Review
PR 요청부터 피드백 대응까지의 코드 리뷰 통합 스킬입니다.
## Part 1: Requesting Review
### PR 생성 전 체크리스트
- [ ] 테스트 통과 확인
- [ ] 린트 에러 없음
- [ ] 변경 범위 명확
- [ ] 커밋 메시지 규격 준수
### PR 설명 템플릿
```markdown
## What
[변경 사항 한 줄 요약]
## Why
[변경 이유]
## How
[구현 방법]
## Testing
- [ ] 단위 테스트 추가
- [ ] 수동 테스트 완료
## Screenshots (UI 변경 시)
[스크린샷]
```
---
## Part 2: Receiving Review
### 피드백 대응 원칙
| 피드백 유형 | 대응 |
|------------|------|
| 버그 지적 | 즉시 수정 |
| 스타일 제안 | 팀 컨벤션 확인 후 수정 |
| 설계 질문 | 의도 설명 또는 개선 |
| 의견 차이 | 논의 후 결정 |
### 대응 패턴
```markdown
# 수용 시
"좋은 지적이에요. 수정했습니다. [커밋 링크]"
# 설명 필요 시
"이렇게 한 이유는 [근거]입니다. 더 나은 방법이 있을까요?"
# 동의 안 할 때
"이해합니다만, [이유]로 현재 방식을 유지하고 싶습니다. 어떻게 생각하세요?"
```
---
## Best Practices
### 리뷰 요청자
- 변경을 작게 유지 (300줄 이하)
- 명확한 컨텍스트 제공
- 셀프 리뷰 먼저
### 리뷰어
- 건설적인 피드백
- 중요도 표시 (Must/Should/Could)
- 칭찬도 함께
## Checklist
- [ ] PR 설명 완성
- [ ] 테스트 통과
- [ ] 피드백 모두 대응
- [ ] 최종 승인 확인
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!
Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...
Ultra-compressed communication mode. Cuts token usage ~75% by speaking like caveman while keeping full technical accuracy. Supports intensity levels: lite, full (default), ultra, wenyan-lite, wenyan-full, wenyan-ultra. Use when user says "caveman mode", "talk like caveman", "use caveman", "less tokens", "be brief", or invokes /caveman. Also auto-triggers when token efficiency is requested.
Routes multi-tool workflows through MCP servers for large datasets and pipelines. Use when Bash tool overhead is limiting throughput on data-heavy tasks.
**Complete production-ready guide for Google Gemini embeddings API** This skill provides comprehensive coverage of the `gemini-embedding-001` model for generating text embeddings, including SDK usage, REST API patterns, batch processing, RAG integration with Cloudflare Vectorize, and advanced use cases like semantic search and document clustering. ---
Interview, source-challenge, verify, save, and ADR-gate fuzzy coding requests into Codex-ready implementation specs. Use when a feature, bugfix, refactor, migration, repo-wide change, or architecture task needs user-verified requirements, source-backed decisions, durable architecture decisions, acceptance criteria, validation commands, rollout notes, saved spec/ADR files, and a Codex execution prompt. Do not use when already fully specified or when the user wants direct implementation now.