sdlc-5-code-review-and-quality

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

2|Updated Apr 30, 2026

Search Tags:#security #refactoring #best-practices #quality-assurance #sdlc #code-review

Ready to run

npx skills add https://github.com/ShaggyD/agent-toolkit --skill sdlc-5-code-review-and-quality

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: sdlc-5-code-review-and-quality
Source: https://github.com/ShaggyD/agent-toolkit/tree/main/development/sdlc-5-code-review-and-quality
Command: npx skills add https://github.com/ShaggyD/agent-toolkit --skill sdlc-5-code-review-and-quality

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill solves the problem of inconsistent, superficial, or skipped code reviews, which often lead to technical debt, security vulnerabilities, and production bugs.

Core Features & Use Cases

Five-Axis Review Framework: Enforces mandatory evaluation of correctness, readability, architecture, security, and performance for every change.
Standardized Quality Gates: Provides clear severity labeling (Critical, Nit, Optional, FYI) to distinguish between mandatory fixes and stylistic suggestions.
Use Case: Before merging a pull request, use this skill to systematically audit the code against the project's architecture and security standards, ensuring that no change enters the main branch without passing rigorous quality checks.

Quick Start

Use the sdlc-5-code-review-and-quality skill to perform a comprehensive five-axis review on the current pull request and generate a summary of findings.

Frequently Asked Questions about sdlc-5-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 software quality?▼

A multi-axis code review evaluates changes across correctness, readability, architecture, security, and performance. This structured approach prevents technical debt, security vulnerabilities, and production bugs by enforcing mandatory quality checks before merging code into the main branch.

How do I perform a structured code review before merging a pull request?▼

Perform a structured code review by systematically auditing the pull request against five axes: correctness, readability, architecture, security, and performance. Apply defined quality gates, verify test coverage, and generate a summary of findings to ensure no change enters the main branch without passing rigorous checks.

How are code review findings categorized to distinguish mandatory fixes from stylistic suggestions?▼

Code review findings are categorized using standardized quality gates with clear severity labels: Critical, Nit, Optional, and FYI. This severity labeling distinguishes between mandatory fixes required before merging and optional stylistic suggestions, ensuring developers focus on necessary code quality improvements.

Does this code review framework enforce change sizing guidelines and test coverage verification?▼

Yes, the code review framework enforces change sizing guidelines and systematically verifies test coverage. It requires adherence to defined quality gates across the software development lifecycle to ensure maintainability and security compliance are met before merging any code changes.

Why do superficial code reviews lead to technical debt and security vulnerabilities?▼

Superficial code reviews lead to technical debt and security vulnerabilities because they skip rigorous evaluation across architecture and security axes. Enforcing a structured, multi-dimensional review process ensures maintainability and security compliance are verified before merging changes, preventing production bugs.