Code Review Standards

Classify code review issues into Critical, High, Medium, and Low severity levels.

1|Updated Feb 5, 2026
One-click install
npx skills add https://github.com/fysoul17/devlyn-cli --skill code-review-standards-fysoul17
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: Code Review Standards
Source: https://github.com/fysoul17/devlyn-cli/tree/main/config/skills/code-review-standards
Command: npx skills add https://github.com/fysoul17/devlyn-cli --skill code-review-standards-fysoul17

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a clear, actionable framework for evaluating code quality, security, and adherence to best practices, ensuring a consistent and high standard across all code reviews.

Core Features & Use Cases

  • Severity Framework: Classifies issues into Critical, High, Medium, and Low severity levels, guiding the review process.
  • Approval Criteria: Defines clear conditions for blocking or approving code changes based on identified issues.
  • Routing Guidance: Recommends specific commands (/devlyn.review, /devlyn.team-review) based on the complexity and sensitivity of the code changes.
  • Use Case: When reviewing a pull request, use this Skill's framework to identify any hardcoded secrets (Critical), ensure functions are not excessively long (High), and check for consistent naming conventions (Medium).

Quick Start

Apply the code review standards to evaluate the attached code diff.

Frequently Asked Questions about Code Review Standards

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

FAQPage Schema
How do I establish consistent code review standards for security and quality?▼

Code review standards provide a structured severity framework classifying issues into Critical, High, Medium, and Low levels to ensure consistent security and quality evaluation across code changes. This framework guides reviewers in identifying hardcoded secrets or long functions.

What is the best way to define approval criteria for blocking a pull request?▼

Defining approval criteria involves setting clear conditions for blocking or approving code changes based on identified issue severities. You block changes when Critical or High severity issues are found, such as hardcoded secrets or excessively long functions, before approving the pull request.

How do I route complex code changes for team review?▼

Routing complex code changes for team review uses specific commands like `/devlyn.review` or `/devlyn.team-review` based on the complexity and sensitivity of the modifications. This ensures appropriate scrutiny is applied to sensitive code changes during the evaluation process.

Can I use this code review framework for any software development workflow?▼

Yes, this code review framework addresses the need for standardized code quality assurance across general software development workflows. It applies a structured severity framework to evaluate code changes regardless of the specific platform, ensuring consistent security and best practices adherence.

When should I not use a structured severity framework for code reviews?▼

A structured severity framework for code reviews may be unnecessary for trivial changes or rapid prototyping where formal approval criteria and routing guidance are not required. It is designed for evaluating complex code changes needing strict security and quality assurance.