code-reviewer

Identify and document critical issues in code changes across pull requests.

Updated Feb 20, 2026
One-click install
npx skills add https://github.com/KrystianYCSilva/math-theory-lib --skill code-reviewer-krystianycsilva
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-reviewer
Source: https://github.com/KrystianYCSilva/math-theory-lib/tree/main/.codex/skills/code-reviewer
Command: npx skills add https://github.com/KrystianYCSilva/math-theory-lib --skill code-reviewer-krystianycsilva

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Code review is essential to catch defects, enforce standards, and improve long-term maintainability in software projects, but teams often miss subtle issues during fast review cycles.

Core Features & Use Cases

  • Thoroughly assess correctness, security, architecture, readability, and performance.
  • Provide actionable feedback and risk-based recommendations for pull requests and refactors.
  • Use in audits of legacy code and engineering best-practice enforcement across repositories.

Quick Start

Provide a detailed, structured code review for the target PR, focusing on the six review dimensions and delivering prioritized recommendations.

Frequently Asked Questions about code-reviewer

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

FAQPage Schema
How do I perform a rigorous code review for a pull request?

Use a structured code review approach across six dimensions: correctness, security, architecture, readability, performance, and coding standards. Outline prioritized recommendations, risk severity, and suggested fixes for architectural boundaries to catch subtle defects during fast review cycles.

What is the best way to review refactoring tasks and legacy code audits?

Review refactoring tasks and legacy code audits by evaluating architectural boundaries, anti-patterns, and coding standards. Document critical issues with actionable recommendations and risk-based suggestions to improve long-term maintainability.

Does this code review approach work for multi-language projects?

Yes, this code review approach works for multi-language projects. It accommodates common programming patterns such as functions, classes, and modules to ensure consistent quality and security assessments across different repositories.

How do I identify security vulnerabilities and anti-patterns during code reviews?

Identify security vulnerabilities and anti-patterns by systematically analyzing code changes for architectural boundary violations and security flaws. Apply risk-based recommendations to document critical issues and provide suggested fixes that enforce engineering best-practices.