angular-migration
Migrate AngularJS Applications to Modern Angular
AngularJS modernization is complex across components, services, routing, forms, and dependency injection. This skill guides staged Angular migration with ngUpgrade patterns, examples, milestones, and validation practices.
Install with my Agent
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Review the Skillstore skill "angular-migration" from https://skillstore.io/skills/sickn33-angular-migration.md and its manifest at https://skillstore.io/api/skills/sickn33-angular-migration/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.Your Agent should still show its plan and request any confirmation required by the security policy.
Agent-readable resources
Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.
Test it
Using "angular-migration". Recommend a strategy for a large AngularJS application that deploys weekly.
Expected outcome:
- Recommendation: use an incremental hybrid migration to preserve weekly delivery.
- Start with shared services, establish ngUpgrade, then migrate isolated feature slices.
- Require compatibility tests, staged releases, rollback checkpoints, and measurable removal targets.
Using "angular-migration". Plan the migration of an AngularJS user management feature.
Expected outcome:
- Convert the shared user service before the controller and directive.
- Bridge the service through dependency injection while both frameworks coexist.
- Migrate routes and forms after component behavior has equivalent tests.
- Remove the AngularJS feature only after staged validation succeeds.
Using "angular-migration". Review readiness to remove ngUpgrade.
Expected outcome:
Confirm that AngularJS modules, downgraded components, upgraded services, legacy routes, and compatibility tests are removed before simplifying bootstrap and dependencies.
Security Audit
SafeAll 50 static findings are false positives caused by code fences, template literals, illustrative same-origin HTTP examples, and ordinary migration language. The skill contains instructional prose and examples; it does not execute commands, perform reconnaissance, or direct data exfiltration. No prompt injection or other intent-level risk was found.
Risk Factors
⚙️ External commands (35)
🌐 Network access (2)
Share & cite this report
Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.
Copy report link
https://skillstore.io/skills/sickn33-angular-migration/audits/5?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown badge
[](https://skillstore.io/skills/sickn33-angular-migration?utm_source=security_passport_badge)HTML badge
<a href="https://skillstore.io/skills/sickn33-angular-migration?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/sickn33-angular-migration/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Embed card
<iframe src="https://skillstore.io/embed/skills/sickn33-angular-migration.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>Academic citations (APA · BibTeX · CFF)
APA citation
sickn33. (2026). angular-migration security audit report (audit version 5) [Author version unspecified]. Skillstore. https://skillstore.io/skills/sickn33-angular-migration/audits/5BibTeX citation
@techreport{sickn33-sickn33-angular-migration-2026,
author = {sickn33},
title = {angular-migration security audit report (audit version 5)},
institution = {Skillstore},
year = {2026},
number = {5},
url = {https://skillstore.io/skills/sickn33-angular-migration/audits/5},
note = {Author version unspecified}
}CITATION.cff
cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "angular-migration security audit report (audit version 5)"
version: "unspecified"
type: report
authors:
- name: "sickn33"
date-released: "2026-07-23"
url: "https://skillstore.io/skills/sickn33-angular-migration/audits/5"
identifiers:
- type: other
value: "skillstore:sickn33-angular-migration:audit:5"
description: "Skillstore immutable audit report identifier"
Compare variants
2 installable variantsEach author remains a separate installable skill. The recommended variant is ranked by Skillstore evidence.
Why this variant is first
sickn33-angular-migration
2026-08-21
wshobson-angular-migration
2026-08-21
Skillstore Score
Why this score Evidence Confidence: HighWhat You Can Build
Plan a Legacy Application Migration
Select a migration strategy, identify milestones, and define rollback and validation checkpoints.
Convert AngularJS Features
Translate controllers, directives, services, routes, and forms into modern Angular patterns.
Review Hybrid Architecture
Evaluate ngUpgrade bootstrap, dependency injection bridges, compatibility testing, and incremental deployment risks.
Try These Prompts
Compare complete rewrite, incremental hybrid, and vertical-slice strategies for my AngularJS application. Recommend one based on team size, release cadence, and risk.
Create a phased AngularJS-to-Angular roadmap for this application. Include services, shared components, routing, forms, feature slices, tests, rollback points, and cleanup.
Review this AngularJS controller, directive, service, and route. Propose Angular equivalents, explain interoperability needs, and list tests required before deployment.
Design an ngUpgrade architecture for this repository. Map bootstrap flow, upgraded and downgraded dependencies, routing ownership, build constraints, migration order, and exit criteria.
Best Practices
- Inventory dependencies and test coverage before selecting a migration strategy.
- Migrate incrementally with compatibility tests, staged releases, and explicit rollback points.
- Track remaining AngularJS ownership and define measurable ngUpgrade exit criteria.
Avoid
- Do not start a complete rewrite without validated scope, staffing, and rollback plans.
- Do not migrate user interfaces before stabilizing shared services and domain logic.
- Do not remove interoperability layers until all dependent AngularJS features are retired.