code-review

Reviews pull requests and code for quality, security, performance, and test coverage.

2|Updated Mar 7, 2025

Search Tags:#code quality #testing #code review #performance #pull request #security audit #solid principles

One-click install

npx skills add https://github.com/AbdelrhmanUZaki/KnowledgeNuggets --skill code-review-abdelrhmanuzaki

Or copy as Structured Prompt for Agent▼

Please help me install this Agent Skill.
Skill: code-review
Source: https://github.com/AbdelrhmanUZaki/KnowledgeNuggets/tree/main/2-setup/shared/gemini/config/skills/code-review
Command: npx skills add https://github.com/AbdelrhmanUZaki/KnowledgeNuggets --skill code-review-abdelrhmanuzaki

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Reviewing code thoroughly and consistently is hard—reviewers often miss security vulnerabilities, performance bottlenecks, or testing gaps, and feedback can be vague or inconsistent across a team. ## Core Features & Use Cases - Structured Review Workflow: Walks through eight review stages covering context, architecture, naming, SOLID principles, error handling, security, performance, testing, and documentation. - Security & Performance Checklists: Audits for SQL injection, XSS, hardcoded secrets, N+1 queries, and resource leaks with concrete vulnerable/fixed code examples. - Constructive Feedback Guidance: Provides templates for prioritized, specific, respectful review comments with severity levels (critical, important, nice-to-have). - Use Case: When a teammate opens a pull request, use this Skill to systematically check the diff against quality, security, and testing checklists, then produce prioritized actionable feedback. ## Quick Start Review this pull request diff for code quality, security vulnerabilities, and missing test coverage, then give me prioritized feedback.

Frequently Asked Questions about code-review

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

FAQPage Schema

What are common code review anti-patterns to watch for?▼

Watch for god classes handling unrelated responsibilities, magic numbers instead of named constants, deep nesting instead of early returns, code duplication, dead code, and silent error swallowing. These signal maintainability problems worth flagging.