code-review

Review AEM Edge Delivery Services code changes and pull requests against quality, performance, and security standards.

1|Updated Jun 22, 2026
One-click install
npx skills add https://github.com/aemgdc/aemdev --skill code-review-aemgdc
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: code-review
Source: https://github.com/aemgdc/aemdev/tree/main/.agents/skills/code-review
Command: npx skills add https://github.com/aemgdc/aemdev --skill code-review-aemgdc

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve? Reviewing AEM Edge Delivery Services (EDS) code changes manually is time-consuming and inconsistent, often missing performance regressions, unscoped CSS selectors, security issues, or missing preview URLs before code reaches production. ## Core Features & Use Cases - Dual Review Modes: Run self-review on uncommitted working-directory changes before committing, or review an existing GitHub pull request by number or URL. - Comprehensive Checklists: Validates JavaScript, CSS, HTML, performance (Lighthouse/Core Web Vitals), accessibility, content authoring compatibility, and security against EDS best practices. - Visual Validation: Captures Playwright screenshots at mobile, tablet, and desktop viewports, with optional before/after comparison and block-level captures. - Actionable Fixes: Posts GitHub inline suggestions for one-click fixes, fix commits for complex refactors, or guidance comments for architectural issues. - Use Case: After implementing a new block, run the skill to catch unscoped CSS selectors and leftover console.log statements, capture responsive screenshots, and fix issues before opening the PR. ## Quick Start Ask the AI to review the current uncommitted changes in your AEM EDS project, or provide a pull request number to review an existing PR.

Frequently Asked Questions about code-review

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

FAQPage Schema
How do I review a GitHub pull request for an AEM EDS project?▼

Invoke the skill with a PR number or URL, such as /code-review 123. It fetches the PR diff via the GitHub CLI, validates preview URLs and description, reviews code quality, captures screenshots, and posts a structured review comment with findings.

How do I review uncommitted code changes before opening a PR?▼

Run the skill without a PR number to trigger self-review mode. It inspects modified files with git status and git diff, checks them against EDS standards, captures screenshots of the preview URL, and reports must-fix issues before you commit.

What code quality checks does the review perform?▼

It checks ESLint and Stylelint compliance, block-scoped CSS selectors, mobile-first breakpoints, absence of console debug statements, no frameworks in the critical rendering path, security issues like XSS and committed secrets, and Lighthouse performance scores.

How are screenshots captured for visual validation?▼

The included capture-screenshots.js script uses Playwright to capture full-page screenshots at mobile (375px), tablet (768px), and desktop (1200px) viewports, plus optional block-level captures, and generates markdown for embedding in PR comments.

Can the review automatically fix issues it finds?▼

Yes. For PR reviews it posts GitHub inline suggestions that authors can apply with one click for most fixable issues. Complex multi-file refactors are handled via fix commits pushed to the PR branch, while subjective issues receive guidance comments.

What are the limitations of GitHub inline suggestions for fixes?▼

Suggestions work best for changes under about 20 lines that can be expressed as line replacements. They are unsuitable for changes spanning many files, fixes requiring testing before commit, or architectural decisions with multiple valid approaches.