Skip to content
TrustedSkillsbeta
Back to all skills

Fix Eslint

Checked
otrebu·vlatest·backend

Automatically resolves common ESLint errors and warnings in JavaScript code, streamlining development 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 otrebu/agents --skill fix-eslint -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

otrebu

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 otrebu/agents at bfdafbf23c.

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

Commit
bfdafbf23c
Manifest
plugins/development-lifecycle/skills/fix-eslint/SKILL.md
Scanned
3 files, 348 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 automatically fixes ESLint errors in JavaScript and React code. It analyzes your codebase, identifies violations of ESLint rules, and applies the necessary changes to correct them. The tool aims to streamline development workflows by reducing manual error correction and ensuring consistent coding style.

When to use it

  • Automated Code Cleanup: Integrate into CI/CD pipelines to automatically fix ESLint errors before merging code.
  • Large Codebases: Quickly address a large number of ESLint violations in existing projects.
  • Enforcing Coding Standards: Maintain consistent coding style across a team by automatically correcting deviations from defined rules.
  • New Project Setup: Ensure new projects adhere to established ESLint configurations from the start.

Key capabilities

  • Automatic ESLint error correction
  • JavaScript and React code support
  • Integration with CI/CD pipelines (implied)
  • Enforcement of coding standards

Example prompts

  • "Fix all ESLint errors in this file: src/components/MyComponent.js."
  • "Run ESLint and automatically fix any violations found in the entire project."
  • "Correct the code style according to our team's ESLint configuration."

Tips & gotchas

  • Ensure an ESLint configuration (.eslintrc.js, .eslintrc.json, etc.) is already present in your project for this skill to function correctly.