Catalog
fauziyasin-s2m4qw/upgrade-oxc

Upgrade oxc, run codegen, and fix any breaking changes.

v1.0LATEST
NewUpdated Jul 19, 2026

Upgrade OXC

CRITICAL: Run each step sequentially ONE AT A TIME. Wait for each command to FULLY COMPLETE before proceeding to the next step. DO NOT run multiple commands in parallel - they have dependencies on each other.

Steps

  1. git checkout main && git pull origin main
  2. just setup
  3. npm view @oxc-project/types version - note the version
  4. Edit pnpm-workspace.yaml: update @oxc-project/runtime, @oxc-project/types, oxc-minify, oxc-parser, oxc-transform to the version from step 3 (use =x.y.z format)
  5. cargo search oxc_allocator --limit 1 - note the version
  6. cargo search oxc_resolver --limit 1 - note the version
  7. Edit Cargo.toml: update oxc, oxc_allocator, oxc_ast, oxc_ecmascript, oxc_minify_napi, oxc_parser_napi, oxc_transform_napi, oxc_traverse to version from step 5; update oxc_resolver, oxc_resolver_napi to version from step 6
  8. cargo update oxc oxc_allocator oxc_ast oxc_ecmascript oxc_minify_napi oxc_parser_napi oxc_transform_napi oxc_traverse oxc_resolver oxc_resolver_napi oxc_sourcemap oxc_index
  9. pnpm install - install updated npm packages
  10. cargo check - if there are errors, fix all breaking changes before proceeding. Common breaking changes include renamed types, changed method signatures, or removed APIs. Study the error messages carefully and update the code accordingly.
  11. just update-generated-code
  12. just test-update
  13. just ued
  14. just roll - run the full build, lint, and test suite. Fix any remaining breaking changes or test failures before proceeding.
  15. git status --short && git diff --stat - verify expected files changed
  16. Summarize the upgrade by reporting: (a) the old and new versions, (b) number of files changed, (c) any breaking changes that were fixed, and (d) notable changes in the diff

Overall Score

78/100

Grade

B

Good

Grades are signals, not a certification. Always review a skill yourself before use.

Safety

82

Quality

76

Clarity

80

Completeness

70

Summary

This skill guides an agent through upgrading the OXC compiler library in a Node.js/Rust monorepo, including updating dependencies, running code generation, and fixing breaking changes. It provides a linear 16-step sequence of git, npm, cargo, and just commands that must be executed sequentially to safely manage multi-language dependency updates and their downstream effects.

Detected Capabilities

git operations (checkout, pull, status, diff)file editing (pnpm-workspace.yaml, Cargo.toml)npm/pnpm package management (npm view, pnpm install)cargo package management (cargo search, cargo update, cargo check)custom build tool execution (just setup, just update-generated-code, just test-update, just ued, just roll)code analysis and error handling (breaking changes assessment)shell command execution

Trigger Keywords

Phrases that agents use to match this skill to user intent.

upgrade oxc libraryupdate compiler dependenciesoxc version bumpcargo oxc updatenpm oxc upgrademonorepo dependency syncfix breaking changes

Use Cases

  • Upgrade OXC compiler to the latest version in a monorepo project
  • Manage synchronized npm and cargo dependency updates for a multi-language codebase
  • Regenerate code after updating OXC and verify all tests pass
  • Identify and fix breaking changes introduced by OXC library updates
  • Document dependency upgrade changes for commit history

Quality Notes

  • Clear sequential execution requirement stated upfront (CRITICAL note prevents accidental parallelization)
  • Step-by-step instructions with logical dependencies well-defined
  • Includes specific file locations to edit (pnpm-workspace.yaml, Cargo.toml) with clear version format guidance
  • Error handling guidance provided for cargo check step (study error messages, fix breaking changes)
  • Final validation step with git status and diff verification ensures expected changes
  • Summarization requirement at the end helps document the upgrade
  • Instructions assume familiarity with cargo, npm, pnpm, and just tool ecosystem — little hand-holding for each command
  • No guidance on rollback strategy if something fails partway through
  • Dependencies between steps are implicit in the sequence but not explicitly cross-referenced
Model: claude-haiku-4-5-20251001Analyzed: Jul 19, 2026

Reviews

Add this skill to your library to leave a review.

No reviews yet

Be the first to share your experience.

Use fauziyasin-s2m4qw/upgrade-oxc in your dev environment

Command Palette

Search for a command to run...