code-review

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

Updated Mar 27, 2025
One-click install
npx skills add https://github.com/jfoxx/residentportal --skill code-review-jfoxx
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-review
Source: https://github.com/jfoxx/residentportal/tree/main/.skills/code-review
Command: npx skills add https://github.com/jfoxx/residentportal --skill code-review-jfoxx

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill automates the process of reviewing code for AEM Edge Delivery Services projects, ensuring adherence to quality, performance, accessibility, and best practices, thereby reducing manual review time and catching issues early.

Core Features & Use Cases

  • Automated Code Validation: Checks JavaScript, CSS, and HTML against established standards.
  • Performance & Accessibility Checks: Identifies potential performance bottlenecks and accessibility issues.
  • Visual Validation: Captures screenshots for visual verification of changes.
  • Actionable Feedback: Provides specific suggestions and fixes directly within pull requests.
  • Use Case: Before merging a new feature into the main branch, run this Skill to automatically validate all code changes, identify any potential bugs or performance regressions, and ensure the code meets project standards.

Quick Start

Use the code-review skill to review the current uncommitted changes in your working directory.

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 projects?

Automate code review for AEM Edge Delivery Services by validating JavaScript, CSS, and HTML against quality, performance, and accessibility standards, providing actionable feedback and visual screenshot validation.

What's the best way to check accessibility and performance in EDS code changes?

Check accessibility and performance in EDS code changes by running an automated validation that identifies potential bottlenecks and compliance issues, offering specific suggestions and fixes before merging into the main branch.

Does the code review process support visual validation of uncommitted changes?

Visual validation of uncommitted changes is supported; the process captures screenshots to verify UI modifications visually, ensuring that code changes do not introduce unexpected visual regressions before committing.

Can I use Playwright to validate JavaScript and CSS in pull requests?

Playwright is used to validate JavaScript and CSS in pull requests by capturing visual screenshots and executing automated checks, ensuring code changes meet established project standards and best practices.

When do I need automated code validation for AEM EDS?

Automated code validation for AEM EDS is needed before merging new features into the main branch to catch bugs early, identify performance regressions, and ensure adherence to quality standards without manual review time.