Skip to content
TrustedSkillsbeta
Back to all skills

Eslint Vitest Rule Tester

Checked
antfu-collective·vlatest·testing·MIT

Helps with ESLint, Vitest as part of testing, debugging, and quality assurance 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 antfu-collective/eslint-vitest-rule-tester --skill eslint-vitest-rule-tester -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

antfu-collective

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 antfu-collective/eslint-vitest-rule-tester at 8b669e7c26.

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

Commit
8b669e7c26
Manifest
skills/eslint-vitest-rule-tester/SKILL.md
Scanned
1 file, 146 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, eslint-vitest-rule-tester, automates the process of testing ESLint rules. It executes a rule against a provided test suite and verifies that the output matches an expected result. This ensures that newly created or modified ESLint rules function as intended and maintain code quality.

When to use it

  • Developing new ESLint rules: Automatically validate your rule's behavior with comprehensive tests.
  • Maintaining existing ESLint rules: Ensure changes don’t introduce regressions by running automated test suites.
  • Continuous Integration (CI): Integrate testing into CI pipelines for consistent and reliable validation of ESLint rules.
  • Code Reviews: Quickly verify the correctness of rule modifications during code review processes.

Key capabilities

  • Automated execution of ESLint rules against test suites.
  • Verification of output against expected results.
  • Integration with existing testing frameworks (Vitest).

Example prompts

  • "Run tests for my new ESLint rule, my-custom-rule."
  • "Verify the changes I made to the no-unused-vars rule."
  • "Execute the test suite for the import/order rule and report any discrepancies."

Tips & gotchas

  • Requires a properly configured Vitest environment with ESLint integration.
  • The accuracy of the results depends on the quality and completeness of the provided test suite.