Code Review
/Code Review
Review code for AEM Edge Delivery Services projects. Use for self-review before committing, or to review pull requests with one-click GitHub suggestions.
- Author
- adobe ↗
- Repository
- helix-tools-website ↗
- Licence
- Apache-2.0
- Last repository change
- 24.10.2026
Assessment and security
- Files in this package
- 4
- Scripts
- 1
- HTML comments
- 1
- URLs in SKILL.md
- 3
No signals detected. Repository changed on 24.10.2026, without references to retired models or APIs.
Apache-2.0, otwarta: można używać i zmieniać, z zachowaniem licencji i informacji o zmianach.
- 1 scripts in this package. Review them before installing, as Claude may execute them.
- SKILL.md zawiera komentarze HTML (1). Nie widać ich w podglądzie Markdown, a model je czyta.
Scripts: scripts/capture-screenshots.js
What it does and when to use it
Review code for AEM Edge Delivery Services projects. Use for self-review before committing, or to review pull requests with one-click GitHub suggestions.
Original author description
Review code for AEM Edge Delivery Services projects. Use for self-review before committing, or to review pull requests with one-click GitHub suggestions.
How it works
- Modes
- Review Criteria
- Priority Levels
- Output Format
SKILL.md preview
---
name: Code Review
description: Review code for AEM Edge Delivery Services projects. Use for self-review before committing, or to review pull requests with one-click GitHub suggestions.
---
# Code Review
Review code for AEM Edge Delivery Services (EDS) projects.
## Modes
### Mode 1: Self-Review (Local Development)
Use before committing to catch issues early.
**Invoke:** `/code-review` (no PR number)
**Process:**
```bash
git status # See modified files
git diff # See changes
git diff --staged # See staged changes
```
**Output:** Report issues directly so the developer can fix them before committing.
**Optional - Capture screenshots** for visual validation:
```bash
cd .claude/skills/code-review/scripts
npm install
node capture-screenshots.js https://{branch}--helix-tools-website--adobe.aem.page/{path}
```
---
### Mode 2: PR Review (Automated or Manual)
Use to review an existing pull request.
**Invoke:** `/code-review <PR-number>` or automatically via GitHub Actions
See **Output Format → PR Review Mode** below for the full process.
---
## Review Criteria
**PR Structure (PR mode only):**
- Preview URL: `https://{branch}--helix-tools-website--adobe.aem.page/{path}` or `https://{branch}--helix-tools-website--adobe.aem.live/{path}` (both `.aem.page` and `.aem.live` are accepted)
- Clear description of what changed and why
**JavaScript:**
- Linting passes (ESLint airbnb-base)
- No `eslint-disable` without justification
- No CSS in JavaScript (use CSS classes)
- No debug console.log statements
- `aem.js` must NOT be modified
**CSS:**
- Linting passes (Stylelint)
- All selectors scoped to block: `.block-name .selector`
- No `!important` without justification
- Mobile-first with standard breakpoints (600px, 900px, 1200px)
**Security:**
- No secrets committed
- No XSS vulnerabilities (sanitize user input)
**Performance:**
- No libraries in critical path
- Consider IntersectionObserver for heavy operations
For detailed checklists, see `resources/review-checklist.md`.
## Priority Levels
- **BLOCKING:** Must fix (security, linting failures, breaking changes)
- **SHOULD FIX:** High priority (performance, accessibility, code quality)
- **CONSIDER:** Nice-to-have improvements
---
## Output Format
### Self-Review Mode
Report findings directly:
```markdown
## Code Review
### Files Reviewed
- `blocks/my-block/my-block.js`
- `blocks/my-block/my-block.css`
### Issues Found
**BLOCKING:**
- `my-block.js:45` - Remove console.log debug statement
**SHOULD FIX:**
- `my-block.css:12` - Selector `.title` needs block scoping
### Ready to Commit?
- [ ] Fix blocking issues above
- [ ] Run `npm run lint`
```
### PR Review Mode
Complete phases in order. **No write API calls until Phase 2.**
**Phase 1: Gather information**
```bash
gh pr view <PR-number> --json title,body,headRefName,files,headRefOid
gh pr diff <PR-number>
```
Read changed files for context. Complete your full analysis before proceeding.
**Phase 2: Clean up previous bot comments**
Fetch IDs first, then delete each one individually (avoid `$(...)` substitution):
```bash
# Inline review comments
gh api repos/{owner}/{repo}/pulls/<PR-number>/comments --jq '[.[] | select(.user.login == "claude[bot]") | .id] | .[]'
# For each id returned: gh api -X DELETE repos/{owner}/{repo}/pulls/comments/<id>
# Issue-level comments
gh api repos/{owner}/{repo}/issues/<PR-number>/comments --jq '[.[] | select(.user.login == "claude[bot]") | .id] | .[]'
# For each id returned: gh api -X DELETE repos/{owner}/{repo}/issues/comments/<id>
# Pending (unsubmitted draft) reviews — these are left behind when event field is missing
gh api repos/{owner}/{repo}/pulls/<PR-number>/reviews --jq '[.[] | select(.user.login == "claude[bot]" and .state == "PENDING") | .id] | .[]'
# For each id returned: gh api -X DELETE repos/{owner}/{repo}/pulls/<PR-number>/reviews/<id>
```
**Phase 3: Post inline suggestions**
Post a suggestion for **every BLOCKING or SHOULD FIX issue where a concrete one-line-or-few-line fix exists**. Inline suggestions are the primary output — the summary in Phase 4 should reference them, not replace them.
Only skip a suggestion if:
- The fix spans multiple files or requires architectural changes
- The affected lines are not present in the diff (e.g. surrounding context lines only)
`position` = 1-based line number counting from the `@@` header line in the unified diff.
Use the `headRefOid` value from Phase 1. Use the Write tool to create `/tmp/review-comments.json` with ALL fields (including `commit_id` and `event`), then post with `--input` only — do NOT mix `--field` with `--input` as `--field` values are silently dropped when `--input` is used:
```bash
gh api --method POST repos/{owner}/{repo}/pulls/<PR-number>/reviews --input /tmp/review-comments.json
```
`/tmp/review-comments.json` format:
```json
{
"commit_id": "<headRefOid from Phase 1>",
"event": "COMMENT",
"comments": [
{"path": "FILE", "position": N, "body": "**Fix:** REASON\n\n```suggestion\nCODE\n```"}
]
}
```
**Phase 4: Post summary comment**
Use the Write tool to create `/tmp/review-summary.md`, then post:
```bash
gh pr comment <PR-number> --body-file /tmp/review-summary.md
```
Summary format:
```markdown
<!-- claude-code-review -->
## Code Review
### Issues Found
- [List by severity: BLOCKING / SHOULD FIX / CONSIDER]
### Verdict
[APPROVE / REQUEST CHANGES / COMMENT]
```
Files in this package (4)
- SKILL.md 5 KB
- resources/review-checklist.md 10 KB
- scripts/capture-screenshots.js 8 KB
- scripts/package.json 1 KB
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · adobe/helix-tools-website | 90 | Apache-2.0 |
| Karanlikyolcu/Skils | 90 | MIT |
| purplemacaron/blank | 80 | MIT |
Database snapshot: 13.11.2026 · package version e8a8c73773df (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 89code-review
Use this when reviewing AEM Edge Delivery Services (EDS, Franklin, Helix) code, either self-review at the end of development before opening a PR, or reviewing an existing pull request. Validates block structure, CSS and JS patterns, DOM output, Lighthouse performance, and… - 100testing-blocks
Use this when you have made AEM Edge Delivery Services code changes to blocks, scripts, or styles and need to validate them before opening a pull request. Covers unit testing for utilities and logic, browser testing with Playwright, linting, and guidance on what to test and how. - 96code-review
Use when reviewing GitHub CLI (gh) pull requests. - 100cpp-review
Review C++ code against Google C++ Style Guide. Use when reviewing C++ code, pull requests, or when asked to check code style compliance. - 100create-github-pr
Create GitHub pull requests using the gh CLI. Use when the user wants to create a new PR, submit code for review, or open a pull request. Trigger keywords - create PR, pull request, new PR, submit for review, code review. - 100code-review
Use when code has been written and needs validation before committing, or when the user asks for a code review or security check.