Automated summary
This skill performs thorough code reviews, focusing on code quality, potential bugs, security issues, and best practices.
Strengths
- Systematic analysis with severity classification
- Detects bugs, security flaws, and best practice violations
- Concrete suggestions with code examples and line numbers
Limitations
- Requires read access to source files
- May lack business or architectural context
- Does not replace expert human review
Use this skill when you need a quick, structured code review for a project or specific file.
Do not use it for high-level architectural decisions or full functional validation.
Security analysis
SafeThe skill only uses read-only tools (Read, Grep, Glob) and instructs AI to analyze code, with no destructive commands, network access, or code execution. It does not obfuscate or exfiltrate data.
No concerns found
How this analysis is madeExamples
Review the code in src/app.js for bugs, security issues, and best practices.Analyze the authentication logic in this project for common security vulnerabilities.Review the code in this pull request and suggest improvements for readability and maintainability.name: Code Reviewer description: Performs thorough code review focusing on code quality, potential bugs, security issues, and best practices. Use this when the user asks to review code, check for issues, or perform code analysis. allowed-tools: Read, Grep, Glob
Code Reviewer Skill
This skill helps you perform comprehensive code reviews.
What to Check
-
Code Quality
- Code readability and maintainability
- Proper naming conventions
- Code organization and structure
- DRY (Don't Repeat Yourself) principle
-
Potential Bugs
- Logic errors
- Edge cases handling
- Null/undefined checks
- Off-by-one errors
-
Security Issues
- Input validation
- SQL injection vulnerabilities
- XSS vulnerabilities
- Authentication/authorization issues
- Sensitive data exposure
-
Best Practices
- Error handling
- Resource management
- Performance considerations
- Documentation and comments
Review Process
- Read the code files specified by the user
- Analyze the code systematically
- Provide specific feedback with line numbers
- Suggest improvements with code examples
- Prioritize issues by severity (Critical, High, Medium, Low)
Output Format
Provide feedback in this structure:
- Summary: Brief overview of the code
- Issues Found: List issues by severity
- Recommendations: Specific actionable suggestions
- Good Practices: Highlight what's done well
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-reviewer-mm5t8bd7/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-reviewer-mm5t8bd7' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/code-reviewer-mm5t8bd7/download' --output '.skill-downloads/code-reviewer-mm5t8bd7/SKILL.md.part' && mv '.skill-downloads/code-reviewer-mm5t8bd7/SKILL.md.part' '.skill-downloads/code-reviewer-mm5t8bd7/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, Grep, Glob
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
This file does not provide a usable name/description header for this native procedure. It remains available to download and inspect; use the manual method below.
Manual 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-reviewer-mm5t8bd7/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.