code-review

Review code changes for security, quality, performance, and maintainability issues.

Updated Apr 20, 2026
One-click install
npx skills add https://github.com/hotaq/Sprite_harmess --skill code-review-hotaq
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: code-review
Source: https://github.com/hotaq/Sprite_harmess/tree/main/.codex/skills/code-review
Command: npx skills add https://github.com/hotaq/Sprite_harmess --skill code-review-hotaq

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you evaluate code changes before merge by surfacing bugs, security risks, performance issues, and maintainability concerns in a clear, severity-ranked review.

Core Features & Use Cases

  • Comprehensive Review: Assesses code quality, security, performance, best practices, and maintainability in one pass.
  • File-Level Guidance: Points to specific files and lines, then recommends concrete fixes that are easy to act on.
  • Merge Readiness Decisions: Supports pull request review, major feature validation, and pre-merge quality checks with an explicit recommendation.
  • Use Case: When a team finishes a feature branch, use this Skill to inspect the diff and produce a decision-ready review before approving the change.

Quick Start

Use the code-review skill to review the current diff and return severity-rated findings with file and line references.

Frequently Asked Questions about code-review

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

FAQPage Schema
How do I review code changes for security and performance before merge?▼

Review pull requests by analyzing the feature branch diff to surface bugs, security risks, and performance issues, returning severity-rated findings with specific file and line references for actionable fixes.

What's the best way to check pull request quality and maintainability?▼

The best way to check pull request quality is to perform a comprehensive review assessing code quality, security, performance, and maintainability in one pass, generating a decision-ready review before approving the change.

Can I get file-level guidance and concrete fixes for my feature branch diff?▼

Yes, you can get file-level guidance by inspecting the feature branch diff, which points to specific files and lines and recommends concrete fixes that are easy to act on for pre-merge quality checks.

How do I validate a major feature implementation for merge readiness?▼

Validate major feature implementations by inspecting the diff to produce a decision-ready review, applying severity-ranked findings and architectural status checks to support an explicit merge readiness decision.