Gate Angular upgrades on Ivy-only readiness. Use when the project is moving to Angular 13+ and View Engine or ngcc compatibility must be explicitly resolved before the upgrade can proceed.
Scanned 10/2/2026
npx -y skills add janpereira-dev/ngAutoPilot --skill angular--ivy--angular-ivy-only-v13-gate --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Angular Ivy Angular Ivy Only V13 Gate?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/janpereira-dev-angular-ivy-angular-ivy-only-v13-gate)More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.
---
id: angular.ivy.angular-ivy-only-v13-gate
name: Angular Ivy Only v13 Gate
description: >
Gate Angular upgrades on Ivy-only readiness. Use when the project is moving to Angular 13+ and View Engine or ngcc compatibility must be explicitly resolved before the upgrade can proceed.
stack:
- Angular
- TypeScript
category: ivy
status: stable
version: 0.10.0
owner: NgAutoPilot
triggers:
- Ivy only
- View Engine
- ngcc
compatibility:
angular:
min: "13"
---
# Angular Ivy Only v13 Gate
## Purpose
Gate Angular upgrades on Ivy-only readiness.
## When to Use
- The project is moving to Angular 13+.
- View Engine or ngcc compatibility must be reviewed.
## When Not to Use
- The project is already Ivy-only.
## Required Inputs
- libraries
- ngcc status
- View Engine artifacts
## Procedure
1. Review Ivy readiness.
2. Identify blockers.
3. Decide gate status.
## Do
- Keep the gate explicit.
## Do Not
- Do not pass the gate with unresolved blockers.
## Review Checklist
- [ ] Ivy readiness is known.
- [ ] Blockers are explicit.
## Expected Output
1. Ivy gate decision.
## Exit Criteria
- Ivy gate is explicit.
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!