Automated summary
A code review skill that frames the analysis of code or a pull request through checklists for prerequisites, review ordering, and points to verify in design, security, and readability.
Strengths
- Enforces a clear priority order: blocking issues (security, crashes) before simple ones (typos) then complex ones (logic, design)
- Explicit checklists covering design, security, and readability that are easy to follow
- Sets the tone of the review by listing forbidden moves (personal attacks, unsupported rejection, style-only nitpicks)
- Reminds the reviewer to confirm prerequisites: PR goal, blast radius, related specs and tickets
Limitations
- Provides no language-, framework-, or static-analysis-specific rules
- No scoring rubric or required output format for the review comments
- Security checks stay generic (input validation, authorization, sensitive data leakage) with no audit depth
Use it when you need to review a PR or existing code and produce structured feedback before merging.
Avoid it for deep security audits, compliance reviews, or fine-grained performance analysis, which need dedicated expertise and tooling.
Security analysis
SafeThe skill contains only code-review checklists and process guidance; it declares no tools and gives no commands that read, modify, exfiltrate, or execute anything. No destructive or obfuscated actions are present.
No concerns found
How this analysis is madeExamples
Review this PR that adds a new endpoint to the user service. Go through blocking issues first (security, crashes), then simple ones, then logic and design, and tell me what must be fixed before merge.Before I merge this branch, run a final code review: check single responsibility, duplication, input validation, authorization checks, and naming clarity. Flag any blocking issue.I need to read and comment on a colleague's changes to the payment module. Apply the code review skill: verify the PR goal and impact scope, then give evidence-based feedback on design, security, and readability.name: code-review description: コードやPRをレビューする際に使用。品質、保守性、よくある問題をカバー。
Code Review
📋 実行前チェック(必須)
このスキルを使うべきか?
- [ ] PRをレビューする?
- [ ] コード品質をチェックする?
- [ ] 他者のコードを読む?
- [ ] マージ前の最終確認を行う?
前提条件
- [ ] PRの目的を理解しているか?
- [ ] 変更の影響範囲を把握しているか?
- [ ] 関連する仕様・チケットを確認したか?
禁止事項の確認
- [ ] 個人攻撃になるコメントをしようとしていないか?
- [ ] 根拠なく否定しようとしていないか?
- [ ] スタイルの好みだけで指摘しようとしていないか?
- [ ] ブロッキングイシューを見逃していないか?
トリガー
- PRレビュー時
- コード品質チェック時
- 他者のコードを読む時
- マージ前の最終確認時
🚨 鉄則
可読性最優先。書く時間より読まれる時間が長い。
レビュー順序
- ブロッキング: セキュリティ、クラッシュ
- シンプル: タイポ、インポート
- 複雑: ロジック、設計
チェックポイント
設計
- 単一責任か
- 重複がないか(DRY)
- 適切な抽象化レベルか
セキュリティ
- 入力検証があるか
- 認可チェックがあるか
- 機密情報が漏れていないか
可読性
- 命名は明確か
- 複雑すぎないか
- コメントは適切か
🚫 禁止事項まとめ
- 個人攻撃になるコメント
- 根拠なき否定
- スタイル好みだけの指摘
- ブロッキングイシューの見逃し
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-msh3uudw/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-msh3uudw' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/code-review-msh3uudw/download' --output '.skill-downloads/code-review-msh3uudw/SKILL.md.part' && mv '.skill-downloads/code-review-msh3uudw/SKILL.md.part' '.skill-downloads/code-review-msh3uudw/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.
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-msh3uudw/SKILL.md' && test -s '.skill-downloads/code-review-msh3uudw/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/code-review' && cp -R '.skill-downloads/code-review-msh3uudw' '.claude/skills/code-review'Cursor
test -f '.skill-downloads/code-review-msh3uudw/SKILL.md' && test -s '.skill-downloads/code-review-msh3uudw/SKILL.md' && mkdir -p '.cursor/skills' && test ! -e '.cursor/skills/code-review' && cp -R '.skill-downloads/code-review-msh3uudw' '.cursor/skills/code-review'Codex
test -f '.skill-downloads/code-review-msh3uudw/SKILL.md' && test -s '.skill-downloads/code-review-msh3uudw/SKILL.md' && mkdir -p '.agents/skills' && test ! -e '.agents/skills/code-review' && cp -R '.skill-downloads/code-review-msh3uudw' '.agents/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-msh3uudw'openskills read 'code-review-msh3uudw'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-msh3uudw/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.