Automated summary
This skill structures a multi-dimensional code review covering security, quality, performance, and maintainability, filtering findings through an 80% confidence threshold.
Strengths
- Four weighted dimensions (security 30%, quality 25%, performance 20%, maintainability 25%) that prevent one-sided reviews
- An 80% confidence gate that curbs false positives and keeps the report low-noise
- Explicit zero tolerance for empty catch blocks, always classified as critical
- Produces a normalized Router Contract (STATUS, BLOCKING, REQUIRES_REMEDIATION, issue counts) consumable by an automated workflow
Limitations
- Dimension weights are fixed and do not adapt to the project's context
- Relies only on Read, Bash, Grep, and Glob tools, with no test execution or dynamic analysis
- The 80% threshold can discard real but uncertain problems, especially subtle concurrency defects
Use it during a code review step in a BUILD, DEBUG, or REVIEW workflow that needs a structured assessment and a machine-readable report.
Avoid it for exploratory or mentoring reviews where low-confidence observations or stylistic preferences should be discussed.
Security analysis
SafeThe skill defines a code-review methodology and only declares read-oriented tools (Read, Grep, Glob) plus Bash for inspection. There are no destructive commands, exfiltration instructions, obfuscated payloads, or attempts to disable safety controls, so listing it presents no meaningful execution risk.
No concerns found
How this analysis is madeExamples
Fais une revue de code complète de la branche feature/payments en appliquant les quatre dimensions et génère le Router Contract.Review src/api/handlers.ts for error handling gaps and flag any empty catch blocks as critical issues.Audite ce module d'authentification selon l'axe sécurité de code-review-patterns et liste uniquement les problèmes avec au moins 80 % de confiance.name: code-review-patterns description: Multi-dimensional code assessment across security, quality, performance, and maintainability with confidence-gated reporting (>=80%) and Router Contract generation. allowed-tools: Read, Bash, Grep, Glob
Code Review Patterns
Overview
Structured patterns for multi-dimensional code review with strict confidence gating. Only issues with >=80% confidence are reported. Zero tolerance for empty catch blocks.
Four Dimensions
Security (weight: 30%)
- Injection vulnerabilities (SQL, XSS, command)
- Authentication and authorization patterns
- Secrets handling (no hardcoded credentials)
- Input validation and sanitization
Quality (weight: 25%)
- Naming conventions and consistency
- Code structure (SRP, cohesion, coupling)
- Error handling completeness
- Type safety (no
anyescapes)
Performance (weight: 20%)
- Algorithmic complexity (flag O(n^2) or worse)
- Resource and memory leaks
- Database query efficiency (N+1)
- Caching opportunities
Maintainability (weight: 25%)
- Documentation (JSDoc/TSDoc for public APIs)
- Test coverage adequacy
- Readability (function length, nesting depth)
- Tech debt markers (TODO, FIXME)
Confidence Gating
- Only report issues with confidence >= 80%
- Empty catch blocks are always critical (100% confidence)
- Classify: critical, high, medium, low
- Include actionable remediation for each issue
Router Contract
Every review must produce: STATUS, BLOCKING, REQUIRES_REMEDIATION, issue counts.
When to Use
- Code review step in BUILD workflow
- Fix review in DEBUG workflow
- Full REVIEW workflow
Agents Used
code-reviewer(primary consumer)silent-failure-hunter(error handling dimension)
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-patterns-mrzxupyf/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-patterns-mrzxupyf' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/code-review-patterns-mrzxupyf/download' --output '.skill-downloads/code-review-patterns-mrzxupyf/SKILL.md.part' && mv '.skill-downloads/code-review-patterns-mrzxupyf/SKILL.md.part' '.skill-downloads/code-review-patterns-mrzxupyf/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, Bash, 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
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-patterns-mrzxupyf/SKILL.md' && test -s '.skill-downloads/code-review-patterns-mrzxupyf/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/code-review-patterns' && cp -R '.skill-downloads/code-review-patterns-mrzxupyf' '.claude/skills/code-review-patterns'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-patterns-mrzxupyf'openskills read 'code-review-patterns-mrzxupyf'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-patterns-mrzxupyf/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.