angular-reviewer

name	angular-reviewer
description	Review Angular components, signals, RxJS, forms, routing, state, accessibility, testing, and bundle performance.
version	1.0.0
since	2026-08-27
last_modified	2026-08-27
authors	["platform-engineering"]
stability	stable
min_platform_version	{"codex":"unknown","amazon-q":"unknown","antigravity":"unknown","auggie":"unknown","bob":"unknown","claude-code":"unknown","cline":"unknown","codebuddy":"unknown","continue":"unknown","costrict":"unknown","crush":"unknown","github-copilot":"unknown","gitlab-duo":"unknown","factory":"unknown","forgecode":"unknown","opencode":"unknown","openhands":"unknown","cursor":"unknown","roo-code":"unknown","kiro":"unknown","junie":"unknown","gemini-cli":"unknown","iflow":"unknown","kilocode":"unknown","kimi":"unknown","lingma":"unknown","pi":"unknown","qoder":"unknown","qwen":"unknown","windsurf":"unknown","ollama":"unknown"}
deprecated_since	null
replaces	null
supersedes	[]
changelog	[{"version":"1.0.0","date":"2026-08-27","change":"Initial generated production-ready SDLC / DevSecOps skill"}]

Angular Reviewer

Purpose

Review Angular applications for component architecture, smart and dumb component separation, RxJS subscription management, change detection strategy, lazy loading, Angular 17 standalone components and signals, reactive forms, and NgRx or state management correctness. Treat regulatory, security, and operational references as review and evidence guidance, not legal advice.

Goal and behavioral contract

The authoritative Goal and artifact references are defined in descriptor.yaml. Capability boundaries, identity and delegation requirements, tool permissions, data boundaries, invariants, approval requirements, output contract, and operational limits are defined in contract.yaml. MCP/A2A trust boundaries and the reviewed execution closure live in integrations/ and dependencies.yaml; ASPS and assurance requirements live in assurance.yaml.

Treat those declarations as mandatory execution constraints. skcr validates requirements but does not claim verification or enforce them at runtime.

When to use

• Angular best practices decisions, controls, or operating practices need independent review.
• A change affects Angular best practices artifacts such as Angular component and template, RxJS observable and subscription, Angular module or standalone component configuration, reactive form definition, lazy-loaded route configuration, state management store or signal.
• The user needs evidence-oriented findings for risks such as memory leak from unsubscribed Observable in component lifecycle, change detection running too frequently due to missing OnPush strategy, business logic embedded in component instead of service, form validation missing on submit allowing invalid data submission, eager loading of feature module increasing initial bundle size, signal or store mutation bypassing immutability causing unpredictable state.
• Audit, security, operations, or platform stakeholders need a concise readiness position.
• Existing documentation, tickets, tests, or logs must be turned into actionable remediation items.

Operating model

1. Identify the relevant Angular best practices artifacts, owners, systems, environments, and review boundary.
2. Compare the available artifacts against expected signals such as Angular DevTools change detection cycle profiler, RxJS subscription audit with takeUntilDestroyed or async pipe, bundle size analysis with source-map-explorer, reactive form validator coverage, lazy route chunk boundary in build output, NgRx state trace or signal debugger.
3. Separate confirmed gaps from assumptions, missing evidence, and advisory improvement opportunities.
4. Rate findings by operational, security, compliance, customer, and auditability impact.