review-code

Review code for correctness, security, performance, and testing deficiencies.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/JGcode3675/gcs-os --skill review-code-jgcode3675
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: review-code
Source: https://github.com/JGcode3675/gcs-os/tree/main/home/james/claude-config/skills/review-code
Command: npx skills add https://github.com/JGcode3675/gcs-os --skill review-code-jgcode3675

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill provides a thorough, structured code review that highlights correctness bugs, security flaws, performance bottlenecks, code quality issues, and gaps in test coverage, delivering actionable feedback before code is merged.

Core Features & Use Cases

  • Correctness Checks: Detect logical errors, edge‑case handling, and inconsistent error management.
  • Security Audits: Identify input validation problems, injection risks, auth/authz weaknesses, and exposure of secrets.
  • Performance Review: Spot N+1 queries, inefficient algorithms, missing caching, and unnecessary memory usage.
  • Quality Assessment: Evaluate naming, abstraction levels, DRY violations, and alignment with project conventions.
  • Testing Guidance: Verify critical path coverage, edge‑case tests, and meaningful test assertions.
  • Use Cases: Ideal for reviewing pull requests prior to merge, auditing legacy codebases, or ensuring compliance with security and performance standards.

Quick Start

Use the review-code skill to analyze the proposed changes in my pull request and list critical findings.

Frequently Asked Questions about review-code

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

FAQPage Schema
How do I perform a code review for correctness and security on a pull request?

Code reviews for pull requests involve analyzing proposed changes to identify logical errors, edge-case handling, input validation problems, and auth weaknesses. The process generates severity-ranked findings with file and line references, offering concrete fix suggestions for thorough quality assurance.

What is the best way to find security flaws and performance bottlenecks in a legacy codebase?

Auditing a legacy codebase for security and performance requires a comprehensive review that spots N+1 queries, inefficient algorithms, missing caching, injection risks, and exposure of secrets. This delivers actionable feedback highlighting critical deficiencies before merging.

Does this code review process check test coverage and edge-case tests?

Yes, code review checks test coverage by verifying critical path coverage, edge-case tests, and meaningful test assertions. It evaluates testing guidance to ensure comprehensive quality assurance across the codebase, highlighting gaps in test coverage alongside correctness and performance issues.

Can I use static analysis to evaluate code quality and DRY violations across multiple languages?

You can apply static analysis across languages to evaluate code quality and DRY violations, assessing naming, abstraction levels, and alignment with project conventions. The review works on pull requests, code commits, or entire codebases to ensure thorough quality assurance.

What kind of fix suggestions can I expect from a comprehensive code review?

Comprehensive code reviews generate severity-ranked findings with file and line references, offering concrete fix suggestions for identified correctness bugs, security flaws, performance bottlenecks, and code quality issues. This delivers actionable feedback directly applicable before code merging.