What problem does it solve? Reviewing code in an Umbraco 17 project requires platform-specific knowledge that generic review checklists miss — null-returning published content APIs, alias collisions, unauthenticated custom endpoints, and per-request view-model costs. This Skill supplies those CMS-specific checks so reviewers catch defects that only manifest in Umbraco's rendering and content model. ## Core Features & Use Cases - Security and code-quality checks: Flags secrets serialized into client-visible markup, missing null guards on published content, alias traps, unauthenticated custom endpoints, hand-edited generated models, and manual .uda schema edits. - Performance review patterns: Identifies per-request view-model construction, N+1 content-tree traversal, media resolution in loops, missing caching on sitewide fragments, and synchronous form handlers without cancellation or deadlines. - Accessibility guidance: Covers editor-authored rich-text output, backoffice web-component extensions, and multiplied severity of defects in shared block views. - Use Case: When reviewing a pull request that adds a new listing page and a contact form endpoint, apply these rules to catch an unauthenticated POST endpoint, an N+1 media lookup in the listing loop, and a missing CancellationToken on the form handler. ## Quick Start Review this Umbraco 17 pull request diff using the umbraco-17-review-rules checklist and report findings by severity.
