← ClaudeAtlas

frontend-change-quality-reviewlisted

Review frontend changes for correctness, types, architecture, accessibility, performance, security, naming, tests, and maintainability. Use for pull requests, diffs, patches, or pre-merge quality audits.
SHIHAOZOU/ai-frontend-engineering-skills · ★ 0 · Code & Development · score 73
Install: claude install-skill SHIHAOZOU/ai-frontend-engineering-skills
# Frontend Code Review Skill For the Simplified Chinese reference, read `references/zh-CN.md` when the user communicates primarily in Chinese or requests Chinese output. ## Purpose Find actionable defects and risks in changed code while separating blocking issues from optional improvements. ## When to Use Use for pull request review, local diff review, release readiness, or acceptance-criteria verification. ## Inputs - Diff or changed files - Requirement and acceptance criteria - Repository rules and validation output - Runtime evidence when available ## Outputs - Findings ordered by severity - File and line references - Evidence, impact, and focused remediation - Validation gaps and residual risk ## Workflow 1. Read the requirement and repository instructions. 2. Inspect the full diff and affected call paths. 3. Verify behavior against acceptance criteria. 4. Check types, architecture, state, errors, accessibility, performance, security, naming, and tests. 5. Reproduce high-risk findings where practical. 6. Report only actionable findings with evidence. 7. Summarize validation gaps after findings. ## Decision Tree ```mermaid flowchart TD A[Potential issue] --> B{Caused by this change?} B -->|No| C[Do not report as a finding] B -->|Yes| D{Observable impact or concrete risk?} D -->|No| E[Optional note only] D -->|Yes| F{Blocks correctness, safety, or release?} F -->|Yes| G[High severity] F -->|No| H[Medium or low severity] ``` ## Checklist - [ ] Fi