oxc-project/oxc
3 skills5.6k installs64.5k starsGitHub
Install
npx skills add https://github.com/oxc-project/oxcSkills in this repo
1Migrate OxlintMigrate-Oxlint is an agent skill for solo builders maintaining JS/TS codebases who want ESLint-level coverage with Oxlint’s performance profile. It walks through running the official @oxlint/migrate CLI at the project root, translating flat ESLint configuration into Oxlint’s JSON config and calling out when type-aware rules require extra packages. The skill fits the ship phase because linting is how indie teams enforce consistency without a dedicated platform team: faster local and CI runs mean you actually run the linter before every push. It is also relevant during build when scaffolding a new monorepo and during operate when reducing CI minutes on aging ESLint stacks. The workflow is deliberately procedural—run migration, inspect generated .oxlintrc.json, optionally enable type-aware migration flags, then validate rule parity—so coding agents do not improvise incompatible configs. Use when asked explicitly to migrate, convert, or switch from ESLint to Oxlint rather than for greenfield lint setup from scratch.3.7kinstalls2Migrate OxfmtMigrate-oxfmt is a procedural agent skill for solo and indie builders who want to replace Prettier or Biome with Oxfmt in a JavaScript or TypeScript project without guessing at config parity. Oxfmt advertises itself as a high-performance, Prettier-compatible formatter, and the skill centers on the official one-shot migration commands rather than manual option hunting. The workflow starts with choosing the source formatter, runs the automated migrator to emit `.oxfmtrc.json`, and walks through what gets translated—ignore patterns, Tailwind class sorting, package.json sorting, and Biome’s split between global and JavaScript-specific formatter keys. Use it when someone asks to migrate, convert, or switch formatting tooling, or when you are standardizing a monorepo on a faster formatter before wiring format-on-save and CI checks. After migration you typically validate output on representative files and update npm scripts so format and check commands call Oxfmt instead of the old tool.1.9kinstalls3Performance Lint RulesPerformance Lint Rules is a narrow meta skill for contributors working on the Oxc linter in Rust. It applies only when editing rule implementations under crates/oxc_linter/src/rules/, explicitly not parser, formatter, or unrelated crates. Solo maintainers and indie OSS contributors use it to keep rules fast on large JavaScript and TypeScript codebases: hoist node-kind filters, run inexpensive predicates before semantic analysis, avoid building diagnostics until needed, and prefer the smallest iterable scope including run_once when a full-file pass suffices. The skill encodes how most files are clean and most nodes never match a given rule, so micro-optimizations at the hot path matter at scale. It pairs with general Rust performance practice but is opinionated for Oxc’s lintgen-generated runners. Advanced complexity is appropriate because readers must understand AST shape, rule traits, and allocator costs. Do not invoke for greenfield app features or non-Oxc lint authoring.1installs