nextjs-code-review

Reviews git diffs against the base branch and generates severity-classified code review reports.

Updated Sep 8, 2026
One-click install
npx skills add https://github.com/lucaszhh/agents --skill nextjs-code-review-lucaszhh
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: nextjs-code-review
Source: https://github.com/lucaszhh/agents/tree/main/skills/front/nextjs-code-review
Command: npx skills add https://github.com/lucaszhh/agents --skill nextjs-code-review-lucaszhh

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Manually reviewing pull requests in a Next.js project is time-consuming and inconsistent, often missing architectural violations, missing error states, or convention breaches that tests do not catch. This Skill automates a structured review of the diff against the base branch, producing a severity-classified report with concrete fixes. ## Core Features & Use Cases - Deterministic pre-checks: Runs pnpm run lint and pnpm run typecheck before semantic analysis, blocking approval on violations. - Structured checklist review: Verifies architecture (modules vs app router), conventions (aliases, MUI import restrictions), forms (react-hook-form + zod), React Query patterns, TypeScript quality, and UI states (loading, empty, error). - Severity-classified report: Writes a full report to .agents/reviews/<branch>-review.md using a template, classifying findings as CRÍTICO, ALTO, MEDIO, or BAJO with file, line, and suggested fix, while returning only a synthetic summary in chat. - Use Case: Before merging a feature branch, ask for a review of the diff against develop; the Skill inspects every changed file, flags a hardcoded query key as ALTO, and saves the full report to disk. ## Quick Start Ask the agent to review the diff of your current branch against develop before merging the pull request.

Frequently Asked Questions about nextjs-code-review

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I review a git diff before merging a pull request?▼

Run a three-dot diff against the base branch (git diff base...HEAD) to isolate your changes, then check each modified file against architectural and convention rules. This Skill automates that process and classifies every finding by severity with a suggested fix.

What should a Next.js code review checklist include?▼

A Next.js review checklist should cover business logic placement in modules rather than the app router, lightweight router pages, separated services and hooks, centralized query keys, react-hook-form with zod for forms, and complete UI states for loading, empty, and error.

Can I enforce custom ESLint rules during code review?▼

Yes. The review runs pnpm run lint and pnpm run typecheck as a mandatory pre-check, and additionally verifies custom rules such as restricted @mui imports outside the design system, banned date-fns format imports, and style rules like single quotes and no-console.

When should I not run an automated diff code review?▼

Skip it when a bug is still unfixed (debug first), when changes are purely visual and need a design audit instead, or when the change is under five trivial lines. It is also not meant for planning new features.

Where is the code review report saved?▼

The full report is written to .agents/reviews/<branch>-review.md using the bundled template. The chat response contains only a synthetic summary with the verdict and a table of CRÍTICO and ALTO blocking findings.