upgrade-project

Name: upgrade-project
Availability: InStock
Author: JYbill

Migrate JavaScript/TypeScript projects across toolchains with guided incremental steps.

1|Updated Mar 14, 2025

Search Tags:#typescript #migration #upgrade #prisma #toolchain #nestjs #swc

Ready to run

npx skills add https://github.com/JYbill/bullboard-nestjs --skill upgrade-project

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: upgrade-project
Source: https://github.com/JYbill/bullboard-nestjs/tree/main/.agents/skills/upgrade-project
Command: npx skills add https://github.com/JYbill/bullboard-nestjs --skill upgrade-project

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams upgrade and standardize JavaScript/TypeScript projects across toolchains, frameworks, testing, build, deployment configurations, and project norms, reducing risk and ensuring consistency.

Core Features & Use Cases

Provides a guided, incremental migration workflow for common toolchains and configurations such as Prettier to Oxfmt, ESLint to Oxlint, Jest to Vitest, CJS/ESM, NestJS latest, SWC, Prisma Client generation, and Dockerfile/.dockerignore setups.
Includes references, templates, and a structured plan to minimize changes while keeping migrations auditable and reversible.
Suitable for use cases like upgrading a legacy NestJS project to latest, migrating tooling across a monorepo, or standardizing project standards across teams.

Quick Start

Follow the migration plan to start upgrading your project configuration now.

Frequently Asked Questions about upgrade-project

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I migrate a NestJS project to the latest version safely?▼

To migrate a NestJS project safely, use a guided, incremental workflow that enforces narrow changes, references, and validations. This approach standardizes toolchains and deployment configurations while keeping migrations auditable and reversible.

What is the best way to migrate Jest to Vitest in a TypeScript monorepo?▼

The best way to migrate Jest to Vitest is through an incremental migration plan that minimizes changes and includes validations. This structured approach ensures consistent testing toolchains across your monorepo while reducing migration risk.

Can I migrate CommonJS to ESM and update SWC configurations simultaneously?▼

Yes, you can migrate CommonJS to ESM and update SWC configurations simultaneously. The workflow supports standardizing JavaScript and TypeScript projects across build tools, frameworks, and deployment setups incrementally.

Does this migration workflow support Prisma Client generation and Dockerfile setups?▼

Yes, this migration workflow supports Prisma Client generation and Dockerfile/.dockerignore setups. It provides templates and a structured plan to standardize project configurations, ensuring changes are auditable and reversible.

How do I migrate from ESLint and Prettier to Oxlint and Oxfmt?▼

You can migrate from ESLint and Prettier to Oxlint and Oxfmt using a guided, incremental migration workflow. This process enforces narrow changes and validations to ensure toolchain consistency and reduce risk during standardization.

Are incremental migrations necessary for standardizing TypeScript toolchains?▼

Incremental migrations are necessary for standardizing TypeScript toolchains because they minimize changes and keep the process auditable and reversible. This structured method reduces risk when upgrading frameworks, testing, and deployment configurations.