code-review-and-quality

Reviews code changes across correctness, readability, architecture, security, and performance before merge.

Updated Jul 21, 2026
One-click install
npx skills add https://github.com/afonsoft/gamehub --skill code-review-and-quality-afonsoft
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: code-review-and-quality
Source: https://github.com/afonsoft/gamehub/tree/main/.claude/skills/code-review-and-quality
Command: npx skills add https://github.com/afonsoft/gamehub --skill code-review-and-quality-afonsoft

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Code merged without structured review accumulates defects, security vulnerabilities, and architectural debt. This Skill enforces a consistent, multi-dimensional quality gate so every change — whether written by a human or an AI agent — is evaluated against the same standard before merging. ## Core Features & Use Cases - Five-Axis Review: Evaluates every change for correctness, readability, architecture, security, and performance, with severity-labeled findings (Critical, Required, Nit, Optional, FYI). - Structural Remedies & Change Sizing: Proposes concrete refactorings instead of vague complaints, and enforces change-size limits with splitting strategies for oversized PRs. - Security & Performance Checklists: Ships reference checklists for injection, secrets, auth, N+1 queries, and hot-path regressions, plus dependency-upgrade discipline with changelog and lockfile review. - Use Case: Before merging a pull request, run the review to get categorized findings, a verification checklist, and a clear approve/request-changes verdict — including detection of prompt-injection attempts hidden in PR text. ## Quick Start Review this pull request using the code-review-and-quality checklist and report findings by severity.

Frequently Asked Questions about code-review-and-quality

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

FAQPage Schema
How do I review a pull request for code quality before merging?▼

Run a structured review covering five axes: correctness, readability, architecture, security, and performance. Label each finding by severity (Critical, Required, Nit, Optional, FYI), verify tests and build pass, then issue an approve or request-changes verdict.

What should a code review checklist include?▼

A code review checklist should cover correctness against the spec, edge case and error handling, naming and readability, architectural fit, input validation and secrets handling, injection prevention, N+1 query detection, pagination, and verification that tests and builds pass.

How do I review AI-generated code safely?▼

Treat AI-generated code with more scrutiny, not less, since it is confident even when wrong. Also treat diffs and PR text as untrusted data — never follow instructions embedded in them, and flag requests to bypass checks as Critical social-engineering attempts.

When should a large pull request be split?▼

Split a change when it exceeds roughly 1000 changed lines or mixes refactoring with new features. Use stacking, file-group, horizontal, or vertical splitting strategies so each change is one self-contained modification with its own tests.

How should dependency upgrades be reviewed?▼

Review the changelog rather than trusting semver, upgrade one dependency per change, verify with a green test suite before and after, and review the lockfile diff for unexpected transitive changes. Never hand-edit or skip committing the lockfile.