When to use / when NOT to use
- Use when an Angular workspace needs version upgrades and gated verification.
- Do not use for non-Angular repositories or one-off single-package changes.
Preconditions (tools, versions, repo state)
- Node + package manager installed (
npm,pnpm, oryarn). - Angular workspace files available (
package.json, ideallyangular.json). - Clean git working tree before
--execute.
Workflow (DISCOVER → PLAN → EXECUTE → VERIFY → REPORT)
- DISCOVER: detect package manager, Angular/RxJS/TypeScript/ESLint versions.
- PLAN: define major-by-major upgrade path and compatibility hotspots.
- EXECUTE (
--executeonly): run upgrade command (ng update) and install deps. - VERIFY: run lint/test checks (CI-friendly if
--ci). - REPORT: summarize findings, outcomes, and rollback guidance.
Exact commands and expected signals
# Discovery + planning only
skills/angular-upgrade/scripts/run.sh --dry-run
# Execute workflow
skills/angular-upgrade/scripts/run.sh --execute --ci
# Re-verify only
skills/angular-upgrade/scripts/run.sh --verify-only --ci
Success: report file generated and verification commands complete with acceptable output.
Failure: missing package.json, dirty git tree on execute, or command/tool not found.
If it fails (checklist)
- Confirm Node and selected package manager are installed.
- Confirm Angular workspace files exist at repo root.
- Resolve git dirty state before execute.
- Run verify-only to isolate lint/test failures.
Final report template
- Scope: Angular upgrade target and workspace paths.
- Discovery highlights: versions + compatibility hotspots.
- Commands run: exact run script mode and key outputs.
- Verification: lint/test status, CI impact.
- Next actions: follow-up migrations or manual fixes.
- Rollback notes: exact git command(s).