code-review-and-quality

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

Updated Mar 28, 2026
One-click install
npx skills add https://github.com/1J6K21/build4good --skill code-review-and-quality-1j6k21
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-review-and-quality
Source: https://github.com/1J6K21/build4good/tree/main/.gemini/skills/code-review-and-quality
Command: npx skills add https://github.com/1J6K21/build4good --skill code-review-and-quality-1j6k21

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provides a consistent, multi-dimensional quality gate that prevents regressions and technical debt by evaluating code changes for correctness, readability, architecture, security, and performance before they enter the main branch.

Core Features & Use Cases

  • Five-axis evaluation: Systematically assess correctness, readability & simplicity, architecture fit, security risks, and performance implications.
  • Structured feedback and verdicts: Produce labeled findings (Critical, Important, Nit, Optional), suggested fixes, and a clear approve/request-changes decision for CI or human reviewers.
  • Use Case: Use this Skill to review pull requests, refactors, bug fixes, and AI-generated code to ensure tests, verification stories, and change descriptions are adequate before merging.

Quick Start

Run a multi-axis code review of the provided change, returning categorized findings, severity labels, suggested fixes, verification steps, and a final approve or request-changes verdict.

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

Code review for AI-generated code applies a multi-axis evaluation to identify correctness, readability, architecture, security, and performance issues. It produces categorized findings with suggested fixes and a final verdict to prevent regressions before merge.

What is the best way to structure code review feedback for CI integration?

Structured code review feedback for CI requires categorized findings labeled by severity such as Critical, Important, or Nit. This format provides suggested fixes, verification guidance, and a clear approve or request-changes verdict for automated gating.

Does this code review approach assess architecture fit and performance implications?

Yes, this code review approach assesses architecture fit and performance implications. It systematically evaluates code changes across five axes, ensuring modifications align with structural design and do not introduce performance bottlenecks.

How do I review refactors and bug fixes to prevent technical debt before merge?

Reviewing refactors and bug fixes to prevent technical debt requires a multi-dimensional quality gate. By checking adequacy of tests and verification stories, it ensures changes are evaluated for readability and security before entering the main branch.

Can I use multi-axis code review for AI-generated code changes?

Yes, you can use multi-axis code review for AI-generated code changes. It evaluates proposed changes for correctness, readability, and security risks, returning categorized findings and a final verdict to ensure quality before merging.