code-review-and-quality

Review code changes across correctness, readability, security, and performance.

4|Updated Jun 10, 2026
One-click install
npx skills add https://github.com/mymx2/foreman --skill code-review-and-quality-mymx2
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-review-and-quality
Source: https://github.com/mymx2/foreman/tree/main/.agents/skills/code-review-and-quality
Command: npx skills add https://github.com/mymx2/foreman --skill code-review-and-quality-mymx2

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill addresses the lack of consistency and rigor in code reviews by providing a structured, multi-dimensional framework that ensures every change is evaluated for correctness, readability, architecture, security, and performance before merging.

Core Features & Use Cases

  • Five-Axis Review: Standardizes evaluation across correctness, readability, architecture, security, and performance.
  • Quality Gates: Defines clear approval standards and severity-based feedback labels to prevent technical debt and ensure high-quality merges.
  • Use Case: Use this skill when reviewing a complex pull request to ensure that the implementation is not only functional but also maintainable, secure, and aligned with the project's architectural patterns.

Quick Start

Use the code-review-and-quality skill to perform a comprehensive review of the current pull request against the five-axis quality standards.

Frequently Asked Questions about code-review-and-quality

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

FAQPage Schema
How do I perform a multi-dimensional code review for a complex pull request?

Multi-dimensional code review evaluates pull requests across correctness, readability, architecture, security, and performance. This ensures changes are functional, maintainable, and aligned with architectural patterns before merging into production.

What are the best practices for enforcing quality gates during code review?

Quality gates enforce approval standards by categorizing review findings by severity. This structured feedback process prevents technical debt accumulation and ensures only production-grade, reliable code changes are approved for merging.

How does severity-based feedback streamline the merge approval workflow?

Severity-based feedback categorizes code review findings to prioritize critical issues over minor improvements. This categorization streamlines the merge approval workflow by giving developers clear, actionable standards for production-grade reliability.

Can I standardize software architecture evaluation across all pull requests?

Yes, standardizing software architecture evaluation is possible by applying a consistent multi-axis review framework. This ensures every code change is rigorously checked for architectural alignment and quality assurance before merging.

When do I need a structured code review framework instead of manual checks?

A structured code review framework is needed when manual checks lack consistency and rigor. It provides a standardized evaluation process for security, performance, and correctness to prevent technical debt in production software.

Does this code review process evaluate security and performance separately?

Yes, the code review process evaluates security and performance as distinct axes. This multi-dimensional approach ensures both vulnerability prevention and performance optimization are independently verified before merge approval.