Agent skill · writing content · angular
PR Review
Guidelines and tools for reviewing pull requests in the Angular repository.
Why this skill is useful
Codifies specific PR review guidelines and practices for the Angular repository that the AI could infer but now doesn't have to guess.
What it needs
About 6k tokens when loaded. Last updated 2026-08-04. 100,955 stars on the source repository.
What this skill does
PR Review Guidelines When reviewing a pull request for the angular repository, follow these essential guidelines to ensure high-quality contributions: 1. Context & Ecosystem: Keep in mind that this is the core Angular framework. Changes here can impact millions of developers. Be mindful of backwards compatibility. Breaking changes require strict approval processes and deprecation periods. 2. Key Focus Areas: Comprehensive Reviews: You MUST always perform a deep, comprehensive review of the entire pull request. If the user asks you to look into a specific issue, file, or area of concern, you must investigate that specific area in addition to reviewing the rest of the PR's substantive changes. Do not terminate your review after addressing only the user's focal point. Package-Specific & Topic Guidelines: Check if there are specific guidelines for the package or topic being modified in the reference/ directory (e.g., reference/router.md or reference/objectcreatenull.md). Always prioritize these rules for their respective areas. Prototype Collision & Object.create(null) PRs: When reviewing PRs that swap {} for Object.create(null), consult reference/objectcreatenull.md for technical evaluation criteria and rules. Commit Messages: Evaluate the quality of commit messages. They should explain the why behind the change, not just the what. Someone should be able to look at the commit history years from now and clearly understand the context and reasoning for the change. Code Cleanliness: Ensure the code is readable, maintainable, and follows Angular's project standards. Performance: Look out for code that might negatively impact runtime performance or bundle size, particularly in hot paths like change detection or rendering. Testing: Ensure all new logic has comprehensive tests, including edge cases. Do NOT run tests locally as part of your review process. CI handles this automatically, and running tests locally is redundant and inefficient. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills angular/pr_review