Conversation
Keep the CLI's Biome rules until their custom Grit checks have equivalents. Run Oxfmt and Oxlint for the remaining workspaces, and preserve accessibility linting and staged-file isolation. Co-Authored-By: GPT-6 Sol <agent@openai.com>
| @@ -0,0 +1,26 @@ | |||
| { | |||
| "$schema": "./node_modules/oxlint/configuration_schema.json", | |||
| "plugins": ["jsx-a11y"], | |||
There was a problem hiding this comment.
Oxlint plugins replace default set
High Severity
The plugins array lists only jsx-a11y. Oxlint treats that field as a replacement, so the default eslint, typescript, unicorn, and oxc plugins never load. categories.correctness then applies only to accessibility rules, and workspace lint no longer reports the correctness issues this migration is meant to catch.
Reviewed by Cursor Bugbot for commit 8671ccc. Configure here.
…toolkit into chore/oxlint-oxfmt
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes and found 1 potential issue.
There are 2 total unresolved issues (including 1 from previous review).
❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.
Reviewed by Cursor Bugbot for commit d39c63b. Configure here.
| @@ -1,4 +1,4 @@ | |||
| { | |||
| "recommendations": ["biomejs.biome"], | |||
| "recommendations": ["oxc.oxc-vscode", "biomejs.biome"], | |||
There was a problem hiding this comment.
Editor still formats with Biome
Low Severity
Root VS Code settings still set Biome as the default formatter and on-save fixer after biome.json and the root @biomejs/biome dependency were removed. Format-on-save for MCP and root files will fail or apply Biome defaults instead of Oxfmt, fighting the new pre-commit and CI tooling.
Reviewed by Cursor Bugbot for commit d39c63b. Configure here.


Summary
Stacked on #1415 because the current main branch has generated CLI skill-version drift that otherwise fails workspace CI. The PR diff contains only this tooling change.
Validation