Skip to content
TrustedSkillsbeta
Back to all skills

Reviewing Typescript Code

Checked
saleor·vlatest·backend·BSD-3-Clause

Analyzes TypeScript code for potential errors, style inconsistencies, and performance bottlenecks within a Saleor backend context.

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 saleor/configurator --skill reviewing-typescript-code -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

saleor

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 saleor/configurator at 3d1b55a084.

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

Commit
3d1b55a084
Manifest
.claude/skills/reviewing-typescript-code/SKILL.md
Scanned
3 files, 584 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 allows AI agents to analyze and provide feedback on TypeScript code. It can identify potential errors, suggest improvements for readability and maintainability, and ensure adherence to coding standards. The agent leverages its understanding of TypeScript syntax and best practices to offer constructive criticism.

When to use it

  • Code Reviews: Integrate into a CI/CD pipeline to automate initial code review checks before human intervention.
  • Learning TypeScript: Use as a learning tool to understand common pitfalls and improve coding style.
  • Refactoring Existing Code: Get suggestions for improving the structure and clarity of older TypeScript projects.
  • Ensuring Consistency: Maintain consistent coding standards across a team by having the agent enforce rules.

Key capabilities

  • TypeScript code analysis
  • Error identification
  • Style suggestion
  • Adherence to coding standards

Example prompts

  • "Review this TypeScript code for potential errors and suggest improvements: [code snippet]"
  • "Can you check if this function follows best practices for TypeScript development? [function definition]"
  • “Analyze the following code and identify any areas where readability could be improved: [code block]”

Tips & gotchas

The quality of feedback depends on the clarity and completeness of the provided code. Providing context, such as project-specific coding standards or desired architectural patterns, can improve results.