Skip to content
TrustedSkillsbeta
Back to all skills

Typescript React Reviewer

Checked
dotneet·vlatest·backend

Helps with TypeScript, React as part of developing backend services and APIs workflows.

Repository

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 dotneet/claude-code-marketplace --skill typescript-react-reviewer -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

dotneet

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 dotneet/claude-code-marketplace at 07fa7eac95.

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

Commit
07fa7eac95
Manifest
review-tool/skills/typescript-react-reviewer/SKILL.md
Scanned
4 files, 1,188 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

What it does

The typescript-react-reviewer skill is designed to analyze and review TypeScript and React code. It identifies potential bugs, enforces best practices, and ensures code adheres to style guidelines. This tool helps developers maintain high-quality frontend applications by providing actionable feedback on their codebase.

When to use it

  • Before merging a pull request in a React project to catch issues early
  • During code reviews to ensure consistency across the team
  • When refactoring legacy TypeScript/React components for clarity and performance
  • To validate new features or libraries integrated into a React application

Key capabilities

  • Static analysis of TypeScript and React code
  • Detection of common bugs and anti-patterns
  • Enforcement of coding standards and style guides
  • Integration with CI/CD pipelines for automated reviews

Example prompts

  • "Review this React component for potential memory leaks or performance issues."
  • "Check the TypeScript types in this file for consistency and completeness."
  • "Analyze this pull request for code quality, best practices, and adherence to style guidelines."

Tips & gotchas

  • Ensure your project has proper TypeScript configuration files (tsconfig.json) for accurate analysis.
  • The tool may not catch runtime issues or edge cases that require execution context.