Automated summary
This skill provides a complete code review workflow, covering pull request preparation and structured responses to reviewer feedback.
Strengths
- Offers a concrete pre-PR checklist (tests, lint, scope, commit messages)
- Includes a PR description template with What/Why/How/Testing/Screenshots sections
- Supplies ready-to-use reply patterns for each feedback type (accept, explain, disagree)
- Reinforces simple best practices: PRs under 300 lines, self-review first, Must/Should/Could prioritization
Limitations
- Mostly procedural and writing guidance, with no automated code analysis
- Recommendations stay generic and must be adapted to each team's conventions
- No integration is described with GitHub, GitLab, or any specific review tool
Use it when you are about to open a pull request or respond to review comments and want a structured framework.
Do not use it for an in-depth code review that requires actually analyzing the diff, tests, or security.
Security analysis
SafeThe skill contains only code-review process guidance, templates, and checklists. Although Bash is listed as an allowed tool, the instructions do not require or suggest destructive commands, network exfiltration, secret handling, obfuscated payloads, or safety bypasses.
No concerns found
How this analysis is madeExamples
I'm about to open a PR for a 250-line refactor of our auth module. Walk me through the pre-PR checklist and write the PR description for me.A reviewer flagged a potential bug and also suggested renaming my functions. Help me draft replies to both comments following good code review etiquette.A reviewer wants me to restructure my design but I think the current approach is better. Help me write a constructive reply explaining my reasoning and asking for their input.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 설명 템플릿
## What
[변경 사항 한 줄 요약]
## Why
[변경 이유]
## How
[구현 방법]
## Testing
- [ ] 단위 테스트 추가
- [ ] 수동 테스트 완료
## Screenshots (UI 변경 시)
[스크린샷]
Part 2: Receiving Review
피드백 대응 원칙
| 피드백 유형 | 대응 | |------------|------| | 버그 지적 | 즉시 수정 | | 스타일 제안 | 팀 컨벤션 확인 후 수정 | | 설계 질문 | 의도 설명 또는 개선 | | 의견 차이 | 논의 후 결정 |
대응 패턴
# 수용 시
"좋은 지적이에요. 수정했습니다. [커밋 링크]"
# 설명 필요 시
"이렇게 한 이유는 [근거]입니다. 더 나은 방법이 있을까요?"
# 동의 안 할 때
"이해합니다만, [이유]로 현재 방식을 유지하고 싶습니다. 어떻게 생각하세요?"
Best Practices
리뷰 요청자
- 변경을 작게 유지 (300줄 이하)
- 명확한 컨텍스트 제공
- 셀프 리뷰 먼저
리뷰어
- 건설적인 피드백
- 중요도 표시 (Must/Should/Could)
- 칭찬도 함께
Checklist
- [ ] PR 설명 완성
- [ ] 테스트 통과
- [ ] 피드백 모두 대응
- [ ] 최종 승인 확인
From the file to a first result
The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.
View the source and supporting filesThis download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.
1. Download the file
Download SKILL.mdFrom the root of a test project, save the file as .skill-downloads/code-review-workflow-mm78nnlg/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.
Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.
mkdir -p '.skill-downloads/code-review-workflow-mm78nnlg' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/code-review-workflow-mm78nnlg/download' --output '.skill-downloads/code-review-workflow-mm78nnlg/SKILL.md.part' && mv '.skill-downloads/code-review-workflow-mm78nnlg/SKILL.md.part' '.skill-downloads/code-review-workflow-mm78nnlg/SKILL.md'2. Check prerequisites
Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.
Tools declared by the author (check availability in your agent): Read, Glob, Grep, Edit, Write, Bash
No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.
The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.
3. Load the skill
After inspection, copy the complete folder into your project using one of the commands below, then open a new tool session. The command stops if a folder with the same name already exists: compare the files before replacing it.
Claude Code
test -f '.skill-downloads/code-review-workflow-mm78nnlg/SKILL.md' && test -s '.skill-downloads/code-review-workflow-mm78nnlg/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/code-review' && cp -R '.skill-downloads/code-review-workflow-mm78nnlg' '.claude/skills/code-review'OpenSkills
OpenSkills must already be installed. The local install/read procedure is checked with OpenSkills 1.5.0, which requires Node.js ≥ 20.6.0. Catalog slugs are not resolved automatically.
Official OpenSkills installationopenskills install './.skill-downloads/code-review-workflow-mm78nnlg'openskills read 'code-review-workflow-mm78nnlg'Reading should display the installed file content and its base directory. It does not run the skill or install its dependencies.
For an agent that reads AGENTS.md, then sync the index. This command changes AGENTS.md: review the diff before using it.
openskills syncManual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.
4. Try a first task
Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:
Read .skill-downloads/code-review-workflow-mm78nnlg/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.
React Hook Form Best Practices
Development
Master React Hook Form: avoid anti-patterns, manage subscriptions, and handle reset, dirty state, and controlled inputs correctly.
Emotion to Mantine Migration
Development
Migrate Emotion styled-components to Mantine components with style props and CSS modules. Use when converting .styled.tsx files or removing @emotion imports.
Scope Creep Detector
Development
Analyzes git diffs against a stated intent to detect scope creep, unrelated files, broad PRs, and oversized changes, then suggests keep, split, or justify actions.