Automated summary
This skill turns the agent into a structured code reviewer that assesses a diff or pull request for correctness, security, performance, and maintainability, then reports findings in a fixed template.
Strengths
- Follows an explicit four-step workflow, from understanding the intent of the change to summarizing findings.
- Enforces a normalized four-section output (summary, critical issues, suggestions, testing), making reviews comparable across runs.
- Ships a reference checklist (references/review-guidelines.md) to keep edge cases and regressions in scope.
- Can lean on bash and git to read the repo and the diff instead of guessing the surrounding context.
Limitations
- Provides no numeric criteria or severity thresholds, so the line between a critical issue and a suggestion is left to the model's judgment.
- No GitHub/GitLab API integration is described, so posting review comments back to the PR is not covered.
- Not language- or framework-specific; you must supply the repo's own conventions yourself.
Use it when you need to review a diff, pull request, or batch of changes before merging and want organized, actionable feedback.
Skip it for deep security audits, architecture reviews, or automated code fixes, which this skill does not address.
Security analysis
SafeThe skill only provides guidance for reviewing code changes; it does not instruct destructive actions, exfiltration, or execution of untrusted code. Allowed tools bash and git are common for inspecting diffs and repository state, and no risky commands are specified.
No concerns found
How this analysis is madeExamples
Review the changes on my current branch against main, focusing on correctness and edge cases, and flag anything blocking before I open a pull request.Do a code review of this pull request: give me a summary, critical issues, suggestions, and a note on whether the testing coverage is adequate.Here's a diff of my latest commit — review it for security, performance, and maintainability problems and summarize the findings in your standard review format.name: code-review description: Expert code reviewer with deep knowledge of software engineering best practices, design patterns, and code quality standards. Use this skill when reviewing code changes, pull requests, or conducting code quality assessments. license: MIT tags:
- code-review
- quality
- best-practices allowed-tools:
- bash
- git
- markdown metadata: author: laurenceputra version: 1.0.0
Code Review
Provide structured, actionable review feedback focused on correctness, security, performance, and maintainability.
Workflow
- Read the change and understand intent.
- Review for correctness, edge cases, and regressions.
- Check repo-specific constraints and testing coverage.
- Summarize findings using the output template.
Output Format
- Summary
- Critical Issues
- Suggestions
- Testing
References
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/expert-code-review-mmbizjp6/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/expert-code-review-mmbizjp6' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/expert-code-review-mmbizjp6/download' --output '.skill-downloads/expert-code-review-mmbizjp6/SKILL.md.part' && mv '.skill-downloads/expert-code-review-mmbizjp6/SKILL.md.part' '.skill-downloads/expert-code-review-mmbizjp6/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/expert-code-review-mmbizjp6/SKILL.md' && test -s '.skill-downloads/expert-code-review-mmbizjp6/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/code-review' && cp -R '.skill-downloads/expert-code-review-mmbizjp6' '.claude/skills/code-review'Cursor
test -f '.skill-downloads/expert-code-review-mmbizjp6/SKILL.md' && test -s '.skill-downloads/expert-code-review-mmbizjp6/SKILL.md' && mkdir -p '.cursor/skills' && test ! -e '.cursor/skills/code-review' && cp -R '.skill-downloads/expert-code-review-mmbizjp6' '.cursor/skills/code-review'Codex
test -f '.skill-downloads/expert-code-review-mmbizjp6/SKILL.md' && test -s '.skill-downloads/expert-code-review-mmbizjp6/SKILL.md' && mkdir -p '.agents/skills' && test ! -e '.agents/skills/code-review' && cp -R '.skill-downloads/expert-code-review-mmbizjp6' '.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/expert-code-review-mmbizjp6'openskills read 'expert-code-review-mmbizjp6'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/expert-code-review-mmbizjp6/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.