Ask Claude to Set Up Biome for Linting and Formatting
Swapping out ESLint and Prettier for Biome cuts config sprawl and makes linting up to 35x faster — but bootstrapping it correctly across a TypeScript project is fiddly. One prompt takes care of everything.
Ask Claude to replace our ESLint and Prettier setup with Biome. Detect the current eslint and prettier configs, migrate any custom rules, add a biome.json, and update package.json scripts and the CI pipeline to use biome check and biome format.
Claude will read your existing .eslintrc and .prettierrc, translate any project-specific rules into Biome equivalents, generate a biome.json tuned to your stack, and wire up the lint and format scripts. If you're on a monorepo, it will also handle workspace-level config inheritance.
A few things to tell Claude upfront so it makes the right call:
- Whether you want
biome check --writeto auto-fix on save in CI or fail loudly - Your target Node/Bun version (affects some parser options)
- If you use
.editorconfig, Claude can reconcile it with Biome's formatter settings
After the migration, ask Claude to run a quick diff between the old and new lint outputs so you can spot any rules that didn't carry over cleanly.
One prompt replaces two tools, hundreds of config lines, and a handful of slow CI steps.
Log in to leave a comment.
Set up Claude Code as an automated reviewer in your CI pipeline — on every pull request, it reads the diff, checks for bugs, security issues, missing tests, and convention violations, then posts its findings as a PR comment. Your human reviewers get a head start because the obvious issues are already flagged before they look.
Before deploying, tell Claude to read your project — migrations, environment variables, queue workers, scheduled tasks, caching, third-party integrations — and generate a deployment checklist that's specific to your app. Not a generic "did you run migrations?" list, but one that knows YOUR infrastructure and catches the things YOUR deploy can break.
Instead of writing a README from memory or copying a template, tell Claude to read your project and generate one that's actually accurate — real setup instructions from your config, real architecture from your directory structure, real API examples from your routes, and real prerequisites from your dependency files.