code-review
Reviews code against project-specific standards for Next.js and TypeScript.
Install
mkdir -p .claude/skills/code-review-gh0stfrk && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/15160" && unzip -o skill.zip -d .claude/skills/code-review-gh0stfrk && rm skill.zipInstalls to .claude/skills/code-review-gh0stfrk
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Review code changes in this Next.js portfolio/blog for correctness, security, performance, and maintainabilityKey capabilities
- →Verify code correctness and edge case handling
- →Check TypeScript types for accuracy and justified `any` usage
- →Ensure input validation and user-generated content sanitization
- →Confirm secrets are stored in environment variables, not source code
- →Assess performance by checking for Server Components and `next/image` usage
- →Evaluate maintainability based on file naming, component placement, and styling
How it works
This skill reviews code against predefined checklists for correctness, security, performance, and maintainability, then outputs structured feedback.
Inputs & outputs
When to use code-review
- →Review pull request
- →Check component performance
- →Verify security practices
About this skill
Code Review
Review the provided code or diff against the project's standards. Flag blocking issues and offer concrete suggestions.
Review Checklist
Correctness
- Does the code behave as described? Are edge cases handled?
- Are TypeScript types accurate? No use of
anywithout justification?
Security
- Are inputs validated before use? Is user-generated content sanitized before rendering?
- Are secrets stored in environment variables, not source code?
- Are error responses free of internal implementation details?
Performance
- Are new components Server Components by default?
- Are images using
next/imagewithwidth,height, andalt? - Are large third-party libraries kept out of Client Components?
Maintainability
- Does the code follow
kebab-casefile names andPascalCasecomponent exports? - Are components placed in the correct directory (
components/vsapp/)? - Is styling done exclusively with Tailwind utilities? Dark mode supported via
dark:variant? - Is the markdown processing going through
lib/blog.tsonly?
Tests
- Do new utilities and components have corresponding tests?
- Do tests verify behavior, not implementation details?
Output Format
For each issue found:
- Severity: Blocking / Suggestion / Nit
- Location: file and line number
- Issue: what is wrong or could be improved
- Recommendation: specific fix or alternative
When not to use it
- →When the project is not a Next.js portfolio/blog
- →When the review does not involve correctness, security, performance, or maintainability
- →When the code changes are not related to the specified checklists
Limitations
- →The skill is specific to a Next.js portfolio/blog project
- →The skill requires styling to be done exclusively with Tailwind utilities
- →The skill expects markdown processing to go through `lib/blog.ts` only
How it compares
This workflow provides a structured, checklist-driven code review process, ensuring consistent evaluation against project standards, unlike an unstructured or ad-hoc review.
Compared to similar skills
code-review side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| code-review (this skill) | 0 | 3mo | No flags | Intermediate |
| reviewing-nextjs-16-patterns | 11 | 8mo | Review | Intermediate |
| vercel-policy-guardrails | 0 | 1mo | Review | Advanced |
| beforemerge-fullstack-architecture-review | 0 | 4mo | No flags | Advanced |
Try saying
Example prompts that trigger this skill in your AI assistant.
You might also like
reviewing-nextjs-16-patterns
djankies
Review code for Next.js 16 compliance - security patterns, caching, breaking changes. Use when reviewing Next.js code, preparing for migration, or auditing for violations.
vercel-policy-guardrails
jeremylongshore
Implement Vercel lint rules, policy enforcement, and automated guardrails. Use when setting up code quality rules for Vercel integrations, implementing pre-commit hooks, or configuring CI policy checks for Vercel best practices. Trigger with phrases like "vercel policy", "vercel lint", "vercel guardrails", "vercel best practices check", "vercel eslint".
beforemerge-fullstack-architecture-review
adrian-coronel
Code review rules for DRY/SOLID layered architecture in fullstack TypeScript applications. Covers dependency direction, service/repository patterns, factory injection, domain entities, security hardening, performance optimization, and code quality patterns. Use this skill when reviewing, writing, or
lint-and-validate
davila7
Automatic quality control, linting, and static analysis procedures. Use after every code modification to ensure syntax correctness and project standards. Triggers onKeywords: lint, format, check, validate, types, static analysis.
agent-tester
ruvnet
Agent skill for tester - invoke with $agent-tester
moai-foundation-quality
modu-ai
Enterprise code quality orchestrator with TRUST 5 validation, proactive analysis, and automated best practices enforcement