Automated summary
Walks an agent through a four-pass code review (security, bugs, quality, performance) and reports findings as severity-tagged issues.
Strengths
- Four-pass checklist keeps each review category from being skipped
- Uniform output format with severity, category, file:line location, issue and suggested fix
- Explicitly targets injection flaws, hardcoded secrets and input validation gaps
- Low risk: the instruction is read-only and does not modify the code
Limitations
- No tooling is run — no linter or SAST; everything relies on the model reading the code
- No language- or framework-specific rules are included
- Severity levels are judgement calls with no defined scoring criteria
Use it for a broad first-pass review of a file, diff or pull request before human sign-off.
Avoid it for compliance-grade security audits or for enforcing project-specific lint rules.
Security analysis
SafeThis skill is a pure instruction/prompt document for reviewing code. It declares no tools, runs no commands, performs no network or filesystem operations, and contains no obfuscated payloads, secret exfiltration, or destructive instructions. The only latent risk is that reviewing untrusted code is an advisory activity, not an execution one, so listing it poses no meaningful risk.
No concerns found
How this analysis is madeExamples
Review this pull request diff for bugs, security issues and style problems, and report each finding with its severity and file:line.Do a security audit of src/auth/session.ts — check for injection, hardcoded secrets and missing input validation.Review the changes in the payments service for code quality, error handling gaps and N+1 query patterns before I merge.name: "code-review" description: "Reviews code for bugs, security issues, style violations, and suggests improvements" triggers: ["review", "code review", "code quality", "lint", "security audit", "PR review"] risk_level: "low"
Instructions
When reviewing code, follow this structured approach:
1. Security Review
- Check for injection vulnerabilities (SQL, XSS, command injection)
- Look for hardcoded secrets or credentials
- Verify proper input validation and sanitization
- Check authentication and authorization patterns
2. Bug Detection
- Look for off-by-one errors, null pointer issues
- Check error handling completeness
- Verify edge cases are handled
- Look for race conditions in concurrent code
3. Code Quality
- Assess naming conventions and readability
- Check for code duplication
- Verify documentation completeness
- Assess test coverage
4. Performance
- Identify potential bottlenecks
- Check for unnecessary allocations or copies
- Look for N+1 query patterns
- Verify proper resource cleanup
Output Format
For each issue found:
[SEVERITY] [CATEGORY] — Brief description
Location: file:line
Issue: What's wrong
Fix: Suggested fix
Severity levels: 🔴 CRITICAL | 🟠 HIGH | 🟡 MEDIUM | 🟢 LOW | 💡 SUGGESTION
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-mryiqhyw/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-mryiqhyw' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/code-review-mryiqhyw/download' --output '.skill-downloads/code-review-mryiqhyw/SKILL.md.part' && mv '.skill-downloads/code-review-mryiqhyw/SKILL.md.part' '.skill-downloads/code-review-mryiqhyw/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-mryiqhyw/SKILL.md' && test -s '.skill-downloads/code-review-mryiqhyw/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/code-review' && cp -R '.skill-downloads/code-review-mryiqhyw' '.claude/skills/code-review'Cursor
test -f '.skill-downloads/code-review-mryiqhyw/SKILL.md' && test -s '.skill-downloads/code-review-mryiqhyw/SKILL.md' && mkdir -p '.cursor/skills' && test ! -e '.cursor/skills/code-review' && cp -R '.skill-downloads/code-review-mryiqhyw' '.cursor/skills/code-review'Codex
test -f '.skill-downloads/code-review-mryiqhyw/SKILL.md' && test -s '.skill-downloads/code-review-mryiqhyw/SKILL.md' && mkdir -p '.agents/skills' && test ! -e '.agents/skills/code-review' && cp -R '.skill-downloads/code-review-mryiqhyw' '.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-mryiqhyw'openskills read 'code-review-mryiqhyw'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-mryiqhyw/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.