code-review-and-quality

Automate five-axis code reviews across correctness, readability, architecture, security, and performance.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a structured, multi-axis review framework to improve code health by guiding reviewers through a comprehensive assessment.

Core Features & Use Cases

  • Five-Axis Review: correctness, readability, architecture, security, and performance evaluation for every change.
  • Quality Gates: ensures tests exist and pass, and that guardrails are in place before merging.
  • Use Case: when evaluating a feature implemented by a teammate or an AI agent, run this review before merging to catch issues early.

Quick Start

Review a pending change with the five-axis checklist and decide to approve, request changes, or add notes based on code health.

Frequently Asked Questions about code-review-and-quality

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

FAQPage Schema
What is a multi-axis code review and how does it improve pull request quality?

A multi-axis code review evaluates pull requests across correctness, readability, architecture, security, and performance, ensuring comprehensive code health assessment before merging changes.

Can I use automated code review to evaluate AI-generated code before merging?

Yes, you can run structured code review checks on AI-generated code to enforce safety checks, verify tests, and maintain architectural alignment prior to merging.

How do I enforce quality gates and security checks during a code review?

You enforce quality gates by running a five-axis assessment that verifies existing tests pass and validates security protocols before approving a pull request.

What is the best way to structure a code review for software engineering teams?

The best way to structure a code review is applying a five-axis checklist covering correctness, readability, architecture, security, and performance to decide on approvals.

When should I request changes on a pull request based on code health?

You should request changes when the multi-axis review identifies failing tests, security vulnerabilities, architectural misalignment, or readability issues impacting overall code health.