Skip to content
Back to skills

Angular Docs Angular Upgrade Report Template

ASecurity

Produce a concise upgrade report that records the current stack, hop taken, gates passed, blockers, and next safe step.

  • 4 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added October 2, 2026
databasesgoangular

Security analysis

A100/100

Scanned October 2, 2026

npx -y skills add janpereira-dev/ngAutoPilot --skill angular--docs--angular-upgrade-report-template --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Angular Docs Angular Upgrade Report Template?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Angular  Docs  Angular Upgrade Report Template
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/janpereira-dev-angular-docs-angular-upgrade-report-template/badge)](https://www.skillsdirectory.com/skills/janpereira-dev-angular-docs-angular-upgrade-report-template)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
id: angular.docs.angular-upgrade-report-template
name: Angular Upgrade Report Template
description: Produce a concise upgrade report that records the current stack, hop taken, gates passed, blockers, and next safe step.
stack:
  - Angular
category: docs
status: stable
version: 0.10.0
owner: NgAutoPilot
triggers:
  - upgrade report
  - migration report
  - hop summary
---

# Angular Upgrade Report Template

Use this skill after an Angular hop, migration, or compatibility gate change.

## Core Rule

```txt
No upgrade is complete until the report says what changed and what remains blocked.
```

## Report Fields

- current stack
- target stack
- hop or change applied
- gates passed
- blockers found
- validation run
- next safe step

## Purpose

Summarize the upgrade state after a hop or migration step.

## When to Use

Use this skill after an Angular upgrade, migration, or compatibility gate change.

## Do

- record the current and target stack
- list blockers and the next safe step

## Do Not

- claim the upgrade is done without validation evidence
- omit blockers from the report

## Review Checklist

- [ ] The upgrade summary is concise.
- [ ] Validation evidence is included.
- [ ] Blockers are visible.
- [ ] The next safe step is identified.

## Output

Return:

1. The upgrade summary.
2. The validation evidence.
3. The remaining blockers.
4. The next safe step.

## Expected Output

Return:

1. A concise diagnosis.
2. The minimal safe change or decision.
3. Validation steps.
4. Risks or rollback notes.

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…