nextjs-code-review
Skill0 starsChanged 3 months agoNo licenceView on GitHub
Full-stack Next.js App Router code review. Asks upfront whether to review the current diff only or the whole codebase, and whether to produce a report only or also apply mechanical fixes. Auto-detects the active git branch, base branch, project structure (app/ layout, route groups, Server vs Client Components), auth strategy, DB layer, Tailwind version, ESLint coverage, and existing component/hook catalog — then reviews against App Router conventions, Server Component defaults, Route Handler discipline, auth guard usage, Zod validation, Tailwind idioms, feature-based file structure, TypeScript safety, testing coverage, and performance patterns. After producing the report, asks whether to apply mechanical + structural fixes in place (never commits, pushes, or stashes). Use when asked to "nextjs code review", "review my next.js changes", "review this branch", "check my diff", "review the whole codebase", "/nextjs-code-review", or before opening a PR on a Next.js App Router project.
- Reads credentials
- Commits and pushes
In this repository38 other files it gives its agents.
- aiml-dudeSkill
- back-end-dudeSkill
- be2-code-reviewSkill
- be-code-reviewSkill
- book-to-productSkill
- browseSkill
- bug-finder-dudeSkill
- bug-huntSkill
- checkerSkill
- code-qualitySkill
- contractor-dudeSkill
- cruise-plannerSkill
- debug-dudeSkill
- designer-dudeSkill
- fe-code-reviewSkill
- fleet-huntSkill
- flight-finderSkill
- front-end-dudeSkill
- general-code-reviewSkill
- h1-reportSkill
- helmSkill
- logo-designSkill
- orchestrateSkill
- pick-programSkill
- plan-dudeSkill
- push-dudeSkill
- qa-dudeSkill
- retro-dudeSkill
- round-trip-stocksSkill
- security-dudeSkill
- seo-dudeSkill
- user-test-2Skill
- user-test-massiveSkill
- user-test-miskariSkill
- user-test-sheevookSkill
- user-testSkill
- user-test-splitsquadSkill
- vuln-researchSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
41 rules. About 0 are common, 18 are distinctive, and 23 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈18
Distinctive · estimate
This author's own choices. Worth a look.
23
Very specific
Tied to their project's names, files or tools. Probably skip.
No licence file, so all rights are reserved — read it at the source. We count its rules but don't quote them. Read them on GitHub.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.