code-review

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

Updated Feb 15, 2026

Search Tags:#testing #code review #performance #security #pull requests #code audit

Ready to run

npx skills add https://github.com/ricable/mcai --skill code-review-ricable

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: code-review
Source: https://github.com/ricable/mcai/tree/main/.agents/skills/code-review
Command: npx skills add https://github.com/ricable/mcai --skill code-review-ricable

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps reviewers quickly inspect code changes for security flaws, performance regressions, maintainability issues, and missing test coverage.

Core Features & Use Cases

Security Review: Flags common risks such as injection flaws, hardcoded secrets, and authorization mistakes.
Performance Review: Surfaces inefficient queries, blocking operations, re-renders, memory leaks, and caching gaps.
Code Quality and Testing Review: Highlights duplication, complex control flow, poor naming, missing error handling, and weak test coverage.
Use Case: Use it when reviewing a pull request to produce a concise, severity-ranked set of findings with suggested fixes.

Quick Start

Ask the code-review skill to review the changed files in your pull request and summarize critical issues, suggestions, and what looks good.

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 in a pull request for security and performance issues?▼

Review code changes by scanning pull request files for injection flaws, hardcoded secrets, inefficient queries, and missing test coverage to produce severity-ranked findings with suggested fixes.

What is the best way to catch hardcoded secrets and authorization bugs before merging code?▼

The best way to catch hardcoded secrets and authorization bugs is to perform a security review on code changes, flagging common risks like injection flaws before the feature branch merges into the main repository.

Can I use automated code review to find performance regressions and memory leaks in frontend code?▼

Yes, you can use automated code review to find performance regressions in frontend code by surfacing inefficient operations, re-renders, memory leaks, and caching gaps across your repositories before merge.

Does code review work for backend API repositories and frontend feature changes?▼

Yes, code review works for backend API repositories and frontend feature changes by applying checks for security flaws, performance inefficiencies, maintainability issues, and weak test coverage across different repository types.

How do I check a code audit for missing test coverage and complex control flow?▼

To check a code audit for missing test coverage, highlight duplication, complex control flow, poor naming, and weak test coverage to ensure maintainability and quality standards are met before merging.