Skip to content
TrustedSkillsbeta
Back to all skills

Eslint Prettier Migration

Checked
aiko-atami·vlatest·backend·MIT

Helps with ESLint, Prettier, migration as part of agent workflows 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 aiko-atami/biomejs-skill --skill eslint-prettier-migration -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

aiko-atami

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 aiko-atami/biomejs-skill at 3a492d0ce7.

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

Commit
3a492d0ce7
Manifest
skills/eslint-prettier-migration/SKILL.md
Scanned
4 files, 170 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 automates the migration of JavaScript projects from ESLint and Prettier to Biome. It handles configuration updates, code formatting, and potential linting rule adjustments, streamlining the transition process. The tool aims for a fully automated experience with minimal manual intervention during the upgrade.

When to use it

  • You're using ESLint and Prettier in your JavaScript project and want to switch to Biome.
  • You have an existing codebase that needs to be formatted and linted consistently with Biome’s ruleset.
  • You are starting a new JavaScript project and prefer to adopt Biome from the beginning, avoiding separate configuration files for formatting and linting.
  • Your team wants to standardize on Biome across multiple projects.

Key capabilities

  • Automated migration from ESLint/Prettier configurations.
  • Code reformatting using Biome's style guidelines.
  • Linting rule adjustments based on Biome’s default settings.

Example prompts

  • "Migrate my project to Biome."
  • "Convert my eslint and prettier configuration to biome."
  • “Run a Biome migration in this directory.”

Tips & gotchas

  • Ensure your project has existing ESLint and Prettier configurations for the skill to function correctly.
  • Review the generated Biome configuration file after migration to ensure it aligns with your team's preferences.