skills.rest
Koryto
KorytoCOMMUNITY
Explore all skills by this author →
GitHub

code-review

Identify risks and improvement opportunities in code changes before merge.

3|Updated Mar 15, 2026
Search Tags:#architecture#maintainability#quality#code-review#software-engineering#review-standards
One-click install
npx skills add https://github.com/Koryto/dotagent --skill code-review-koryto
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: code-review
Source: https://github.com/Koryto/dotagent/tree/main/.agent/skills/code-review
Command: npx skills add https://github.com/Koryto/dotagent --skill code-review-koryto

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Review and assess code changes to surface risks, ensure correctness, and enforce production-grade quality before integration.

Core Features & Use Cases

  • Identify logic bugs, invariants violations, and edge-case gaps in new changes.
  • Evaluate scalability, maintainability, and adherence to established patterns across features, bug fixes, and refactors.
  • Use in mandatory self-review or when a user requests a rigorous code review to mitigate production risk.

Quick Start

Provide a formal code review of the latest changes focusing on correctness, scalability, and long-term maintainability.

Frequently Asked Questions about code-review

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

FAQPage Schema
What is a production-grade code review and what does it evaluate?▼

A production-grade code review assesses code changes to surface correctness issues, regression risk, and architectural misalignments before merge. It evaluates logic bugs, invariants violations, scalability, maintainability, and adherence to established patterns to prevent production defects.

How do I review code changes for logic bugs and edge-case gaps?▼

To review code changes for logic bugs, provide the latest changes for a formal assessment. The review focuses on correctness, identifying invariants violations, and surfacing edge-case gaps to ensure production-ready software quality and prevent integration defects.

Can I use this code review for refactors and bug fixes, not just new features?▼

Yes, you can use this code review for refactors, bug fixes, and new features. It evaluates architectural misalignments, scalability, and long-term maintainability across all code changes to enforce production-grade quality before integration.

When do I need a structured review for software maintainability and regression risk?▼

You need a structured review during pre-merge assessments when evaluating software maintainability and regression risk. It mitigates production risk by enforcing review standards and surfacing improvement opportunities in correctness, scalability, and architecture.

What is the best way to enforce review standards and prevent production defects?▼

The best way to prevent production defects is using structured review criteria during mandatory self-review or pre-merge checks. This enforces production-grade standards by surfacing correctness issues, regression risk, and architectural misalignments in code changes.

Related Skills

Explore More Software Engineering Skills→
zoeyzouzoeyzou

code-review-best-practices

Review pull requests and diffs with structured checklists for security and performance.

Community
Intermediate
lshtramlshtram

finish-task

Verify code quality and merge feature branches into main.

Community
Intermediate
pvillegapvillega
23

bugmagnet

Analyze code and tests to reveal edge-case gaps and coverage holes.

Community
Advanced
ianyimiianyimi
1

Global Coding Style

Enforce global coding style guidelines across multi-language codebases.

Community
Basic