code-review

Review code changes across six dimensions to identify actionable fixes.

Updated Jan 2, 2026
One-click install
npx skills add https://github.com/yuhle-qug/Parking_Management_System --skill code-review-yuhle-qug
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-review
Source: https://github.com/yuhle-qug/Parking_Management_System/tree/main/.agent/skills/code-review
Command: npx skills add https://github.com/yuhle-qug/Parking_Management_System --skill code-review-yuhle-qug

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Code reviews are essential for maintaining software quality but can be time-consuming and inconsistent. This Skill provides a structured, expert review across six focused dimensions to ensure robust, maintainable, and secure code.

Core Features & Use Cases

  • Architecture & Design: Evaluate module boundaries, patterns, and extensibility.
  • Code Quality & Readability: Assess naming, clarity, complexity, refactoring opportunities, and consistency.
  • Security & Dependencies: Identify vulnerabilities, authentication/authorization concerns, and risky dependencies.
  • Performance & Scalability: Highlight hot paths, asynchronous patterns, and resource usage implications.
  • Testing Quality: Review test coverage, isolation, determinism, and meaningful assertions.
  • Documentation & API Design: Ensure clear docs, stable APIs, and developer experience.
  • Use Case: Applicable after major changes or PRs to surface actionable improvements.

Quick Start

Run the review on a codebase by providing the changed files and context; the skill will return a prioritized list of issues and suggested fixes ready for integration.

Frequently Asked Questions about code-review

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

FAQPage Schema
How do I get actionable code review feedback for a pull request?

To get actionable code review feedback, provide the changed files and context to generate a prioritized list of architectural, security, and performance issues with suggested fixes ready for integration.

What is the best way to review code quality and security vulnerabilities in a refactor?

The best way to review code quality and security vulnerabilities during a critical refactor is to evaluate module boundaries, naming clarity, and authentication concerns using structured best-practice checklists.

Can I use automated code review across any programming language or tech stack?

Yes, you can use this code review process across any language or stack because it relies on supplied codebase context and best-practice checklists rather than external tooling or language-specific configurations.

How do I assess testing quality and performance hot paths after major codebase changes?

You assess testing quality and performance hot paths by reviewing test coverage isolation, checking asynchronous patterns, and evaluating resource usage implications to highlight scalability issues.

Does code review work without external dependencies or tooling?

Yes, code review works without external dependencies because it requires no tooling beyond a standard development environment, using supplied context to produce targeted recommendations.