Skip to content
TrustedSkillsbeta
Back to all skills

Typescript Code Review

Checked
jpoutrin·vlatest·backend·MIT

Helps with TypeScript, code review 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 jpoutrin/product-forge --skill typescript-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

jpoutrin

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 jpoutrin/product-forge at 0ebe7aea08.

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

Commit
0ebe7aea08
Manifest
plugins/frontend-experts/skills/typescript-code-review/SKILL.md
Scanned
1 file, 391 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

This skill provides automated TypeScript code review. It analyzes your TypeScript code for common errors, style inconsistencies, and potential improvements based on established best practices. The goal is to improve code quality and reduce technical debt by identifying issues early in the development process.

When to use it

  • Before submitting a pull request: Ensure code adheres to project standards before merging changes.
  • During code refactoring: Identify potential problems introduced during restructuring efforts.
  • For onboarding new developers: Quickly enforce coding style and best practices within a team.
  • Automated CI/CD pipelines: Integrate into your build process for continuous quality checks.

Key capabilities

  • TypeScript linting
  • Style guide enforcement
  • Error detection
  • Code improvement suggestions

Example prompts

  • "Review this TypeScript code for potential errors and style issues: [paste code]"
  • "Can you check if this function adheres to our project's TypeScript coding standards? [paste code]"
  • “Analyze the following code snippet and suggest improvements based on best practices: [paste code]”

Tips & gotchas

  • The skill’s effectiveness depends on a well-defined project style guide. Providing context or configuration files can improve results.