Skip to content
TrustedSkillsbeta
Back to all skills

Typescript Rules

Checked
shinpr·vlatest·backend·MIT

Enforces strict TypeScript coding standards and identifies potential errors within backend codebases.

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 shinpr/claude-code-workflows --skill typescript-rules -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

shinpr

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 shinpr/claude-code-workflows at 0caac066b1.

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

Commit
0caac066b1
Manifest
skills/typescript-rules/SKILL.md
Scanned
3 files, 303 lines
Copies in repo
3 — all of them scanned
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, typescript-rules, enforces and validates TypeScript code against established rules. It helps maintain consistent coding style and prevents common errors within a project. The skill can automatically format code, identify violations of defined rules, and suggest corrections to ensure adherence to best practices.

When to use it

  • Project onboarding: To quickly standardize the codebase for new team members or when integrating external code.
  • Automated linting in CI/CD pipelines: To prevent non-compliant code from being merged into production.
  • Refactoring existing TypeScript projects: To systematically improve code quality and consistency across a large codebase.
  • Enforcing coding standards: To ensure all developers follow the same rules for formatting, complexity, and potential errors.

Key capabilities

  • TypeScript rule enforcement
  • Code formatting
  • Violation identification
  • Correction suggestions

Example prompts

  • "Format this TypeScript file according to project rules."
  • "Check this code snippet for any violations of the TypeScript style guide."
  • "Identify and suggest fixes for potential errors in this component."

Tips & gotchas

This skill requires a pre-existing configuration of TypeScript rules (e.g., ESLint with appropriate plugins). Without such a configuration, it cannot effectively enforce or validate code.