Lint JS/TS

VerifiedSafe

Run the JS/TS linter before opening a PR when only JS/TS files are changed. Fix errors and re-run until clean.

Sby Skills Guide Bot
DevelopmentBeginner
208/30/2026
Claude Code
#lint#javascript#typescript#code-quality#static-analysis

Recommended for

Our review

Runs the JavaScript/TypeScript linter using the project's `./x lint-js` command and iterates on errors until clean.

Strengths

  • Simple and direct command
  • Integrates with existing project setup
  • Automates pre-PR quality checks
  • Supports both JS and TS files

Limitations

  • Only works if the project has the `x` script
  • Only checks JS/TS, not other languages
  • No configuration options beyond running the standard linter
When to use it

Use before opening a pull request that only changes JavaScript or TypeScript files.

When not to use it

Do not use if you changed Rust or other non-JS/TS files, or if the project lacks the `x lint-js` script.

Security analysis

Safe
Quality score85/100

The skill only runs a local repository script './x lint-js' for linting JavaScript/TypeScript. It does not instruct destructive actions, exfiltration, or execution of remote/untrusted content. The allowed tool is explicitly restricted to this command.

No concerns found

Examples

Lint changed JS files
Run lint-js on the JavaScript files I've changed.
Pre-PR TypeScript check
Please lint my TypeScript code before opening the pull request.
Check for lint errors
Check for lint errors in the JS files I modified and fix them.

name: lint-js description: Lint JS/TS code only. Use before opening a PR when only JavaScript or TypeScript files were changed (no Rust). user-invocable: true allowed-tools: Bash(./x lint-js)

Lint JS/TS Code

Run the JS/TS linter:

./x lint-js

If there are lint errors, fix them and re-run until clean.

Related skills