skills.rest
kevindree
kevindreeCOMMUNITY
Explore all skills by this author →
GitHub

code-review-and-quality

Review code changes for correctness, readability, architecture, security, and performance.

Updated May 3, 2026
Search Tags:#code review#performance#refactoring#pull requests#security review#quality gate
One-click install
npx skills add https://github.com/kevindree/geehoo-gateway --skill code-review-and-quality-kevindree
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: code-review-and-quality
Source: https://github.com/kevindree/geehoo-gateway/tree/main/.github/skills/code-review-and-quality
Command: npx skills add https://github.com/kevindree/geehoo-gateway --skill code-review-and-quality-kevindree

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams evaluate code changes before merge so defects, security risks, and maintainability issues are caught early instead of reaching the main branch.

Core Features & Use Cases

  • Multi-axis review: Checks correctness, readability, architecture, security, and performance in one pass.
  • Merge readiness decisions: Separates required fixes from optional suggestions using clear severity labels.
  • Common use cases: Reviewing pull requests, validating bug fixes, assessing refactors, and checking AI-generated code before it ships.

Quick Start

Use this skill to review the change for correctness, readability, architecture, security, and performance, then return clear findings with severity labels and a merge recommendation.

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 code changes for correctness, security, and performance before a merge?▼

Reviewing code changes before merge involves checking correctness, readability, architecture, security, and performance in a single pass, then applying severity labels to separate required fixes from optional suggestions for a merge-ready quality gate.

What is the best way to evaluate AI-generated code before it ships to the main branch?▼

Evaluating AI-generated code requires a multi-axis review that applies test-first inspection, verifies edge-case coverage, and labels severity to catch defects, security risks, and maintainability issues early.

How do I assess a refactoring or bug fix to ensure it is merge-ready?▼

Assessing refactors or bug fixes requires verifying build and manual validation, inspecting edge-case coverage, and applying severity labels to distinguish mandatory fixes from optional suggestions.

Can I use a single code review pass to check both architecture and security vulnerabilities?▼

Yes, a multi-axis code review checks architecture and security vulnerabilities simultaneously, alongside correctness, readability, and performance, returning clear findings with a merge recommendation.

How does a quality gate distinguish between required fixes and optional suggestions in a pull request?▼

A quality gate uses clear severity labels during the review process to categorize findings, separating required fixes that block merges from optional suggestions for improving readability and architecture.

Related Skills

Explore More Software Engineering Skills→
J-PsterJ-Pster
291

requesting-code-review

Generate standardized code-review requests with severity-labeled findings.

Community
Intermediate
whywaitawhywaita

build-validator

Automate post-change build validation across Node.js, Go, Python, and Rust projects.

Community
Intermediate
HomericIntelligenceHomericIntelligence
18

generate-tests

Generate test cases for functions and modules from signatures and expected outputs.

Official
Intermediate
OneWave-AIOneWave-AI
245

code-review-pro

Review code for security vulnerabilities, performance bottlenecks, and maintainability issues.

Official
Basic