skills.rest
guneysol
guneysolCOMMUNITY
Explore all skills by this author →
𝕏@guneysolGitHub

nextjs-audit

Audits changed React and Next.js code against Vercel best practices with severity-ranked findings.

Updated Jul 17, 2026
Search Tags:#diff analysis#code review#best practices#react#vercel#nextjs#performance audit
One-click install
npx skills add https://github.com/guneysol/agent-configs --skill nextjs-audit-guneysol
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: nextjs-audit
Source: https://github.com/guneysol/agent-configs/tree/main/agents/skills/nextjs-audit
Command: npx skills add https://github.com/guneysol/agent-configs --skill nextjs-audit-guneysol

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Reviewing React and Next.js changes for performance and best-practice violations is time-consuming, and generic advice often ignores project-specific decisions. This Skill audits only the changed code against Vercel React best practices, prioritizing high-impact issues like waterfalls, bundle regressions, and hydration problems. ## Core Features & Use Cases - Diff-Focused Audit: Inspects only changed files and applies only the rules relevant to those changes, respecting project AGENTS.md or CLAUDE.md decisions. - Severity-Ranked Report: Groups findings into critical, high, medium, and low, each with category, file and line reference, rationale, and the smallest reasonable fix. - Use Case: After modifying a Next.js data-fetching component, run the audit to catch a sequential-fetch waterfall and unnecessary client-side loading before merging the pull request. ## Quick Start Ask the assistant to audit the changed React and Next.js files in the current diff against Vercel best practices and report the highest-impact issues.

Frequently Asked Questions about nextjs-audit

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

FAQPage Schema
How do I audit Next.js code changes for performance issues?▼

Run the audit on your changed files and it checks them against Vercel React best practices, focusing on waterfalls, bundle size, data fetching, and hydration. Findings are grouped by severity with file and line references and a minimal suggested fix.

What issues does a React and Next.js performance audit catch?▼

The audit prioritizes request waterfalls and unnecessary sequential work, bundle size regressions, server and data-fetching inefficiencies, and re-render or hydration issues. Lower-level JavaScript performance is only flagged when it is material to the change.

Does the audit respect project-specific conventions in AGENTS.md or CLAUDE.md?▼

Yes. Project documentation is read before applying generic guidance, and project decisions override the reference rules. It will not recommend a different server-state library or patterns the project has already decided against.

Does the Next.js audit review the entire codebase?▼

No. It focuses only on the changed files and diff, applying just the rules relevant to that code. It avoids theoretical advice and does not invent issues to fill severity categories.

When should I not use a diff-scoped Next.js audit?▼

Avoid it when you need a full-application baseline review, since it intentionally skips unchanged code. It is designed for reviewing pull requests and incremental changes, not whole-app architecture assessments.

Related Skills

Explore More Software Engineering Skills→
jmmarottajmmarotta

code-simplify

Refactor recently modified code for readability using git diff.

Community
Intermediate
Sridhar-RanganaboinaSridhar-Ranganaboina

dev6-review-fix

Automates triaging review comments, applying fixes across files, and committing descriptive changes.

Community
Advanced
ArthTech-AIArthTech-AI

qa

Run full-stack QA checks with pytest, Jest, ruff, TypeScript, and Playwright.

Official
Intermediate
wilfozwilfoz

perf-lighthouse

Run Lighthouse audits via CLI or Node API and parse performance reports.

Community
Intermediate