Skip to content
TrustedSkillsbeta
Back to all skills

Nextjs Code Review

Checked
giuseppe-trisciuoglio·vlatest·frontend·MIT

Helps with Next.js, code review as part of building frontend UIs and user experiences workflows.

Install on your platform

Showing Claude Code. One command installs this skill into any of the agents below.

  1. 1

    Run this in your project

    terminal
    $ npx skills add giuseppe-trisciuoglio/developer-kit --skill nextjs-code-review -a claude-code
  2. Uses the open-source skills CLI and needs Node.js. Add -g to install it for your user instead of this project.

What we know about this skill

Publisher

giuseppe-trisciuoglio

Taken from the source listing. We haven't verified who controls this account.

Install target

Live repository

Not pinned. Installing fetches whatever the repository holds at the time you run the command.

No human has reviewed this code. The checks below are a static scan of the files at one commit — nobody has run this skill or judged whether it works. A skill runs with whatever access you give your agent, so read the source before you install it.

Automated safety checks

scanned

This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.

  • Declares what it does: passed

    SKILL.md parses and declares a name and a description.

    SKILL.md exists, its frontmatter parses, and it declares a name and a description.

  • No undeclared network calls: passed

    Makes no network calls.

    Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.

  • No obfuscated payloads: passed

    No encoded or obfuscated payloads.

    No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.

  • No credential access: passed

    Reads no keys, tokens, keychains or credential files.

    Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.

  • No pipe-to-shell installers: passed

    No pipe-to-shell or download-and-run installers.

    No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.

  • Pinned to a commit: passed

    Scanned giuseppe-trisciuoglio/developer-kit at fe73fb33a0.

    The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.

Scanned
4 files, 881 lines
This is a static scan, not a review. It reads the skill's files; it does not run them, and it cannot tell you whether the skill is any good or whether the code does what its description says. A skill runs with whatever access you give your agent.
What each check looks for →

About this skill

The nextjs-code-review skill enables AI agents to analyze Next.js application code, identifying potential bugs, performance bottlenecks, and security vulnerabilities within the framework's specific architecture. It provides actionable feedback on component structure, data fetching strategies, and rendering optimizations to ensure high-quality production-ready code.

When to use it

  • Before merging pull requests to catch logic errors or anti-patterns in React Server Components.
  • During refactoring sessions to optimize image optimization and dynamic/static route configurations.
  • When auditing existing codebases for security flaws related to client-side hydration or API routes.
  • To validate that new features adhere to Next.js best practices regarding caching and revalidation.

Key capabilities

  • Analyzes specific Next.js file structures including app and pages directories.
  • Identifies issues with Server Components, Client Components, and the 'use client' directive usage.
  • Reviews data fetching methods like fetch, getServerSideProps, and getStaticProps.
  • Checks for common performance pitfalls such as unnecessary re-renders or missing metadata exports.

Example prompts

  • "Review this Next.js component for potential memory leaks and improper use of the 'use client' directive."
  • "Analyze the API route structure in this file for security vulnerabilities and error handling gaps."
  • "Identify performance bottlenecks in this page's data fetching strategy and suggest optimizations using React Query or SWR."

Tips & gotchas

Ensure the code provided includes necessary context, such as the full component tree or relevant configuration files like next.config.js, to allow for accurate architectural analysis. This skill is specialized for Next.js; it may not provide meaningful feedback on generic React code outside this framework's ecosystem.