angular-upgrade

Upgrade Angular projects one major version with automated commits and validation.

Updated Mar 10, 2026
One-click install
npx skills add https://github.com/LeoFalco/shared-skills --skill angular-upgrade-leofalco
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: angular-upgrade
Source: https://github.com/LeoFalco/shared-skills/tree/main/angular-upgrade
Command: npx skills add https://github.com/LeoFalco/shared-skills --skill angular-upgrade-leofalco

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Upgrading an Angular application across a major version often requires coordinated package updates, framework migrations, dependency compatibility checks, and repeated validation steps; this Skill automates that process and reduces risky manual changes by creating individual commits, running migrations, and verifying the app compiles and tests.

Core Features & Use Cases

  • Targeted Major Upgrade: Detects the current @angular/core major version and upgrades to exactly the next major release.
  • Automated ng update flow: Runs Angular CLI updates for core, CLI, Material/CDK, @angular-eslint, and other ecosystem packages, using --create-commits so each change is reviewed separately.
  • Dependency reconciliation and verification: Regenerates lockfiles, reinstalls dependencies, runs lint, tests, dev server smoke tests, and a production build to catch regressions before pushing changes.
  • Use Case: Maintain an enterprise Angular monorepo and safely advance each application by one major Angular release while preserving a clear audit trail of commits and automated checks.

Quick Start

Run the angular-upgrade skill in the project root to detect the current Angular version, perform ng update steps, and validate lint, tests, and production build.

Frequently Asked Questions about angular-upgrade

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

FAQPage Schema
How do I upgrade an Angular project to the next major version?▼

You can automate an Angular major version upgrade by running ng update with --create-commits and --force for core, CLI, Material/CDK, and @angular-eslint packages. The process regenerates lockfiles and validates success through lint, tests, and production builds.

How does ng update work with Material, CDK, and angular-eslint during a migration?▼

During an Angular migration, ng update applies core, CLI, Material/CDK, and @angular-eslint updates sequentially using --create-commits. This generates discrete commits for each ecosystem package change, ensuring safe dependency reconciliation and a clear audit trail.

Can I use this automated ng update flow for an enterprise Angular monorepo?▼

Yes, you can use this automated ng update flow for an enterprise Angular monorepo. It safely advances applications by one major Angular release while preserving a clear audit trail of automated checks and discrete commits for each dependency change.

What validation steps are required after running an Angular dependency update?▼

Required validation steps after an Angular dependency update include regenerating the lockfile, running linting, executing tests, performing a dev server smoke test, and completing a production build to catch any regressions before pushing changes.

Why does an Angular upgrade require creating individual commits for each package change?▼

An Angular upgrade requires individual commits to reduce risky manual changes and provide a clear audit trail. Using the --create-commits flag with ng update separates framework migrations and ecosystem package updates for easier review and rollback.