Codex, Claude Code and GitHub Copilot custom agents for reviewing and modernizing Angular codebases.
This repository provides reusable agents focused on practical Angular modernization, template maintainability, accessibility, and component-level refactoring opportunities.
The agents were created from real-world usage in Angular projects that migrated from older versions to newer versions and need a safe, incremental way to adopt modern Angular features without unnecessary rewrites.
These agents are designed based on real-world Angular migration scenarios.
Instead of forcing modern Angular syntax everywhere, they help answer:
💡 “Is this change worth doing in this file, right now?”
Focus areas:
- ⚙️ Incremental modernization (Angular 15 → 19)
- 🧩 Maintainability over trends
- ♿ Accessibility-first mindset
- 🚀 Real performance impact (not micro-optimizations)
Many Angular codebases upgrade framework versions but do not immediately adopt newer patterns such as modern control flow, @defer, @let, standalone components, inject(), or signal-based APIs.
This repository helps teams answer a practical question:
💭 When I touch this file, is there an improvement opportunity that is actually worth applying now?
The goal is not to force new syntax everywhere.
The goal is to support scoped, high-signal reviews that improve:
- readability
- maintainability
- accessibility
- performance
| Agent | Purpose |
|---|---|
ng-template-reviewer |
Reviews Angular templates focusing on complexity, logic-heavy HTML, modern control flow (@if, @for), @let, @defer opportunities, self-closing tags, expensive bindings, and structural accessibility. |
ng-component-reviewer |
Reviews Angular component classes for practical modernization (Angular 19), including standalone readiness, inject(), signal-based APIs (input(), output(), queries), state simplification, lazy-loading opportunities, and scoped refactor suggestions. |
This repository currently starts with custom agents.
Custom agents are best for:
- 🔍 Specialized judgment
- 🧩 Focused diagnosis
Examples:
- review this Angular template
- assess modernization opportunity
- classify recommendations by risk
Future skills will cover:
- 🔁 Repeatable workflows
- 📋 Checklists and automation
Examples:
- local code review against
develop/main - Angular feature checklist
- Jest test authoring checklist
- bugfix verification workflow
Model:
- 🤖 Agents → diagnose
- 🧩 Skills → orchestrate
- 📘 Repo instructions → define rules
.github/
agents/
ng-template-reviewer.agent.md
ng-component-reviewer.agent.md
agents/
ng-template-reviewer/
README.md
ng-template-reviewer.agent.md
ng-component-reviewer/
README.md
ng-component-reviewer.agent.md
README.md
LICENSE
You can keep the distributable agent files under agents/<agent-name>/ and copy them into .github/agents/ in the target repository.
Copy the desired .agent.md file into the target repository:
.github/agents/<agent-name>.agent.md
Example:
.github/agents/ng-template-reviewer.agent.md
.github/agents/ng-component-reviewer.agent.md
Commit the files to the repository default branch.
If you want the agents available only in a specific Angular project, add them directly to that project's .github/agents/ directory.
For organization-wide usage, adapt the files to your organization's Copilot custom agent setup and governance model.
Use the ng-template-reviewer agent on this component template.
Focus on template complexity, @if/@for quality, @let opportunities, @defer candidates, self-closing tags, expensive bindings, and structural accessibility.
Do not modify code. Return findings grouped by adoption timing.
Use the ng-component-reviewer agent on this component class.
Focus on standalone value, inject() migration value, signal input/output/query opportunities, signals/computed state, and realistic modernization for this file.
Do not modify code.
These agents follow a few core principles:
-
🧠 Diagnosis first
Do not modify files unless explicitly instructed. -
🧱 Stable Angular only
Focus on stable features through Angular 19. -
🚫 No modernization for novelty
Newer APIs are not always better. -
⚡ Opportunistic modernization
Improve files that are already being touched. -
🎯 Scope control
Separate “do now” vs “backlog”. -
♿ Accessibility and maintainability first
Prioritize clarity and usability over syntax.
For Angular repositories, consider adding this to your AGENTS.md:
# Angular modernization policy
- Prefer stable Angular features only.
- Favor opportunistic modernization in files already being changed.
- Do not force syntax migrations without a clear readability, maintenance, accessibility, or performance gain.
- Keep refactors scoped to the current task unless explicitly asked otherwise.
- Accessibility and testability take precedence over stylistic modernization.
- By default, reviewers should diagnose first and avoid changing files unless explicitly instructed.Contributions are welcome.
Good contributions include:
- ✨ new Angular-focused agents
- 🔍 refinements to review criteria
- 📄 examples of prompts and outputs
- 🎨 PO-UI-specific review rules
- ♿ accessibility improvements
- 🔁 skills for repeatable Angular workflows