code-review-and-quality

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

Updated Feb 9, 2026
One-click install
npx skills add https://github.com/tradertunante/servicecontrol --skill code-review-and-quality-tradertunante
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-review-and-quality
Source: https://github.com/tradertunante/servicecontrol/tree/main/.claude/skills/code-review-and-quality
Command: npx skills add https://github.com/tradertunante/servicecontrol --skill code-review-and-quality-tradertunante

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Conducts multi-axis code review before merges to enforce quality gates and reduce defect rates.

Core Features & Use Cases

  • Five-Axis Review: correctness, readability, architecture, security, and performance.
  • Structured critique guidance for reviews of changes from self, teammates, or agents.
  • Use Case: Before merging PRs, reviews code health and communicates decisions with justified improvements.

Quick Start

Review a proposed change across all five axes and document findings before approving or requesting changes.

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 automate a pull request code review for correctness and security?

A multi-axis code review evaluates proposed changes across correctness, readability, architecture, security, and performance. It provides structured critique and severity labeling to communicate justified improvement decisions before approving merges.

Can I use static analysis to enforce quality assurance gates before merging code?

Yes, static analysis supports quality assurance by enforcing quality gates before merges. The review workflow applies structured evaluation to reduce defect rates across five critical axes of code health.

What is the best way to review agent-authored code changes for architecture and performance?

Reviewing agent-authored code requires a multi-axis evaluation covering architecture and performance alongside correctness, readability, and security. This structured approach documents review decisions and justifies required changes to maintain quality.

Does multi-axis code review work for refactoring existing codebases?

Yes, multi-axis code review works for refactoring existing codebases. It applies the same five-axis structured evaluation to refactors as it does to feature updates or bug fixes, ensuring changes maintain correctness, readability, architecture, security, and performance standards.

How do I document code review decisions and label severity for pull requests?

Documenting code review decisions involves applying structured critique guidance across five axes and assigning clear severity labels. This workflow ensures that review decisions and change justifications are systematically recorded before approving or requesting changes.