code-review

Review AEM Edge Delivery Services code for quality, performance, and accessibility issues.

1|6|Updated Feb 10, 2026
One-click install
npx skills add https://github.com/aemsites/summit-portal --skill code-review-aemsites
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-review
Source: https://github.com/aemsites/summit-portal/tree/main/skills/aem/edge-delivery-services/code-review
Command: npx skills add https://github.com/aemsites/summit-portal --skill code-review-aemsites

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires playwright, and includes scripts (resource) components.

What problem does it solve?

This Skill reduces manual reviewer effort and prevents regressions by automatically auditing AEM Edge Delivery Services code changes for quality, performance, accessibility, security, and adherence to EDS best practices.

Core Features & Use Cases

  • Automated PR & self-review workflows: analyze diffs, validate PR structure, and verify preview URLs before merge.
  • Multi-domain checks: linting (ESLint/Stylelint), performance (Lighthouse/PSI), accessibility, security patterns, and architectural recommendations.
  • Visual validation: capture desktop, tablet, and mobile screenshots (Playwright) for before/after or block-level comparisons.
  • Use case: run a pre-merge review that flags lint errors, accessibility issues, missing preview URLs, performance regressions, and includes one-click suggestion fixes or guidance for maintainers.

Quick Start

Run a code-review on pull request 123 and produce a checklist of lint, accessibility, performance, and security findings with suggested fixes and screenshots.

Frequently Asked Questions about code-review

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate code review for AEM Edge Delivery Services pull requests?

Automated code review for AEM Edge Delivery Services pull requests analyzes repository diffs, PR metadata, and preview URLs to identify quality, performance, accessibility, and security issues before merge. It validates linting, performance metrics, and architectural best practices.

What checks are included in an AEM EDS code review?

An AEM EDS code review includes multi-domain checks for linting via ESLint and Stylelint, performance metrics using Lighthouse, accessibility rules, security patterns, and architectural recommendations to prevent regressions and reduce manual reviewer effort.

Can I use Playwright screenshots for visual validation during a pull request review?

Playwright screenshots enable visual validation during a pull request review by capturing desktop, tablet, and mobile screenshots. These images support before and after comparisons or block-level visual checks to verify UI changes.

Does the code review workflow support self-review of uncommitted changes?

The code review workflow supports self-review of uncommitted changes alongside automated CI runs and manual reviewer checks. It requires access to repository diffs and PR metadata to validate linting, performance, and accessibility standards.

How do I validate accessibility and performance regressions before merging an AEM EDS project?

To validate accessibility and performance regressions before merging an AEM EDS project, run a pre-merge review that flags issues using Lighthouse metrics and accessibility rules. It produces a checklist with suggested fixes for maintainers.

What prerequisites are needed to run an automated AEM EDS code review?

Prerequisites for an automated AEM EDS code review include repository diffs, PR metadata, preview URLs, and optional Playwright tooling for visual validation. These inputs enable comprehensive linting, performance, and security analysis.