code-review-and-quality

Review code against correctness, readability, architecture, security, and performance standards.

Updated Jul 31, 2026
One-click install
npx skills add https://github.com/fsolla/teqo --skill code-review-and-quality-fsolla
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-review-and-quality
Source: https://github.com/fsolla/teqo/tree/main/.agents/skills/code-review-and-quality
Command: npx skills add https://github.com/fsolla/teqo --skill code-review-and-quality-fsolla

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, preventing technical debt, security vulnerabilities, and architectural decay by enforcing a standardized, multi-dimensional evaluation process.

Core Features & Use Cases

  • Five-Axis Review: Systematically evaluates code for correctness, readability, architecture, security, and performance.
  • Structural Remedies: Provides actionable, named refactoring patterns to resolve complex code issues rather than just identifying them.
  • Use Case: Use this skill when preparing a pull request for a new feature to ensure the implementation adheres to project conventions, maintains clean module boundaries, and is free of common security or performance pitfalls before it reaches the main branch.

Quick Start

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

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 pull request?

A multi-dimensional code review evaluates pull requests across five axes: correctness, readability, architecture, security, and performance to ensure software quality and maintainability.

What is the best way to prevent technical debt and architectural decay during refactoring?

Preventing technical debt and architectural decay during refactoring requires a standardized evaluation process that enforces clean module boundaries and provides named structural patterns to resolve code issues.

How do I check my code implementation for security vulnerabilities and performance pitfalls?

Checking code for security vulnerabilities and performance pitfalls involves systematically reviewing the implementation against defined correctness and performance standards before merging changes into the main branch.

Can I use an automated code review process for bug fixes across the development lifecycle?

Yes, an automated code review process applies to bug fixes across the development lifecycle by enforcing a standardized, multi-dimensional evaluation to maintain codebase health.

Does a standardized code review provide actionable remedies for complex software architecture issues?

Yes, a standardized code review provides actionable, named refactoring patterns to structurally resolve complex software architecture issues rather than merely identifying them.