code-review-and-quality

Enforce a 5-axis code review framework for pre-merge pull requests.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Unvetted code merged to the main branch introduces bugs, security vulnerabilities, architectural drift, and unmanageable technical debt that slows down entire engineering teams. This Skill eliminates inconsistent, ad-hoc code reviews by enforcing a standardized, multi-dimensional quality gate for every change.

Core Features & Use Cases

  • 5-Axis Review Framework: Evaluates every change for correctness, readability, architecture, security, and performance to catch issues across all critical dimensions.
  • Structured Review Process: Includes step-by-step guidance for context gathering, test-first review, implementation review, and severity-labeled feedback to make reviews efficient and actionable.
  • Change Management Guidelines: Defines clear sizing rules for pull requests, splitting strategies for large changes, and best practices for change descriptions to keep reviews fast and low-friction.
  • Use Cases: Review PRs from any author (yourself, other agents, human teammates), evaluate post-feature implementation code, assess bug fixes and their associated regression tests, and validate refactoring work before merge.

Quick Start

Use the code-review-and-quality skill to review the attached pull request for adherence to project standards, security vulnerabilities, and overall code health before approving it for merge.

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 enforce consistent pre-merge code reviews for pull requests?

Consistent pre-merge code reviews are enforced by applying a structured 5-axis framework that evaluates correctness, readability, architecture, security, and performance. This standardized process prevents bugs, security vulnerabilities, and technical debt from entering the main codebase.

What is the best way to review code changes for security vulnerabilities before merging?

The best way to review code changes for security vulnerabilities is using a multi-dimensional quality gate that includes dedicated security checks. This ensures unvetted code is analyzed for security risks alongside correctness and architecture before merge approval.

How do I assess bug fixes and regression tests during a code review?

Assess bug fixes and regression tests during a code review by following a structured review process that prioritizes test-first evaluation. This approach validates the associated regression tests and implementation before approving the bug fix for merge.

Can I use a standardized review framework for AI agents and human developers?

Yes, you can use a standardized review framework for AI agents and human developers. It applies uniform code quality standards, severity-labeled feedback, and dead code hygiene checks to all pre-merge review scenarios regardless of the author.

What sizing rules should I apply to split large pull requests for faster reviews?

Sizing rules for splitting large pull requests involve applying defined change management guidelines. These rules outline splitting strategies and best practices for change descriptions to keep reviews fast, low-friction, and highly effective.