Skip to content
Back to skills

Angular Upgrade Angularjs Angularjs Controller To Component Migration

ASecurity

Convert AngularJS controllers into Angular components during modernization. Use when controller-heavy views must become component-based before or during a hybrid migration.

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

Works with

  • api

Security analysis

A100/100

Scanned October 2, 2026

npx -y skills add janpereira-dev/ngAutoPilot --skill angular--upgrade--angularjs--angularjs-controller-to-component-migration --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Angular Upgrade Angularjs Angularjs Controller To Component Migration?

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

Security grade badge for Angular  Upgrade  Angularjs  Angularjs Controller To Component Migration
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/janpereira-dev-angular-upgrade-angularjs-angularjs-controller-to/badge)](https://www.skillsdirectory.com/skills/janpereira-dev-angular-upgrade-angularjs-angularjs-controller-to)

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.upgrade.angularjs.angularjs-controller-to-component-migration
name: AngularJS Controller to Component Migration
description: >
  Convert AngularJS controllers into Angular components during modernization. Use when controller-heavy views must become component-based before or during a hybrid migration.
stack:
  - Angular
  - AngularJS
category: angularjs
status: stable
version: 0.10.0
owner: NgAutoPilot
triggers:
  - AngularJS controller migration
  - controller to component
  - legacy controller
compatibility:
  angular:
    min: "2"
---

# AngularJS Controller to Component Migration

## Purpose

Migrate AngularJS controllers to Angular components.

## When to Use

- Controllers own view logic that should move to components.
- The app is being modernized incrementally.

## When Not to Use

- The controller is not part of the migration scope.
- The app is already component-first.

## Required Inputs

- controller code
- template bindings
- scope usage

## Procedure

1. Extract controller state and methods.
2. Move template logic into Angular component inputs and outputs.
3. Validate behavior.

## Do

- Keep component APIs simple.
- Preserve user-visible behavior.

## Do Not

- Do not keep scope-based coupling.

## Review Checklist

- [ ] Controller responsibilities identified.
- [ ] Component API defined.
- [ ] Tests updated.

## Expected Output

1. Controller migration summary.
2. Component mapping.

## Exit Criteria

- Controllers are no longer required for the migrated view.

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…