Automated summary
This skill guides code review so it becomes a knowledge-sharing practice rather than gatekeeping, by structuring analysis and constructive feedback.
Strengths
- Provides a clear output format with a summary, issues grouped by severity, and clarifying questions
- Systematically covers correctness, security, performance, and maintainability
- Encourages asking clarifying questions when the code's intent is unclear
- Supports mentoring through actionable feedback instead of blocking comments
Limitations
- Does not itself contain detailed checklists; these are delegated to an external resources file
- Does not implement fixes, staying limited to reviewing
- Defines no specific coverage thresholds or metrics
Use it when reviewing a pull request or a set of code changes and you want structured, pedagogical feedback.
Avoid it when there are no code changes to review, or when the task is to fix the code rather than review it.
Security analysis
SafeThis is a pure documentation/instruction skill describing how to conduct code reviews. It declares no tools, contains no shell commands, network calls, file writes, or credential handling, and references only a local markdown resource for expanded guidance. There is no execution surface or destructive behavior to worry about.
No concerns found
How this analysis is madeExamples
Review this pull request: read the context and tests, then give me a summary, issues by severity, and any clarifying questions.Help me establish code review standards for my team based on this repo's conventions, focusing on correctness, security, and maintainability.Review my changes with a mentoring tone: point out the important issues with rationale so I can learn, not just what to change.name: code-review-excellence description: "Transform code reviews from gatekeeping to knowledge sharing through constructive feedback, systematic analysis, and collaborative improvement." risk: safe source: community date_added: "2026-02-27"
Code Review Excellence
Transform code reviews from gatekeeping to knowledge sharing through constructive feedback, systematic analysis, and collaborative improvement.
Use this skill when
- Reviewing pull requests and code changes
- Establishing code review standards
- Mentoring developers through review feedback
- Auditing for correctness, security, or performance
Do not use this skill when
- There are no code changes to review
- The task is a design-only discussion without code
- You need to implement fixes instead of reviewing
Instructions
- Read context, requirements, and test signals first.
- Review for correctness, security, performance, and maintainability.
- Provide actionable feedback with severity and rationale.
- Ask clarifying questions when intent is unclear.
- If detailed checklists are required, open
resources/implementation-playbook.md.
Output Format
- High-level summary of findings
- Issues grouped by severity (blocking, important, minor)
- Suggestions and questions
- Test and coverage notes
Resources
resources/implementation-playbook.mdfor detailed review patterns and templates.
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-excellence-ms1aw5kz/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-excellence-ms1aw5kz' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/code-review-excellence-ms1aw5kz/download' --output '.skill-downloads/code-review-excellence-ms1aw5kz/SKILL.md.part' && mv '.skill-downloads/code-review-excellence-ms1aw5kz/SKILL.md.part' '.skill-downloads/code-review-excellence-ms1aw5kz/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-excellence-ms1aw5kz/SKILL.md' && test -s '.skill-downloads/code-review-excellence-ms1aw5kz/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/code-review-excellence' && cp -R '.skill-downloads/code-review-excellence-ms1aw5kz' '.claude/skills/code-review-excellence'Cursor
test -f '.skill-downloads/code-review-excellence-ms1aw5kz/SKILL.md' && test -s '.skill-downloads/code-review-excellence-ms1aw5kz/SKILL.md' && mkdir -p '.cursor/skills' && test ! -e '.cursor/skills/code-review-excellence' && cp -R '.skill-downloads/code-review-excellence-ms1aw5kz' '.cursor/skills/code-review-excellence'Codex
test -f '.skill-downloads/code-review-excellence-ms1aw5kz/SKILL.md' && test -s '.skill-downloads/code-review-excellence-ms1aw5kz/SKILL.md' && mkdir -p '.agents/skills' && test ! -e '.agents/skills/code-review-excellence' && cp -R '.skill-downloads/code-review-excellence-ms1aw5kz' '.agents/skills/code-review-excellence'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-excellence-ms1aw5kz'openskills read 'code-review-excellence-ms1aw5kz'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-excellence-ms1aw5kz/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.