code-review-and-quality

Review code changes for correctness, readability, architecture, security, and performance issues.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill turns code review into a consistent quality gate, helping teams catch correctness, readability, architecture, security, and performance issues before changes are merged.

Core Features & Use Cases

  • Multi-axis review: Evaluates changes across five dimensions so feedback goes beyond whether the tests pass.
  • Review discipline: Encourages clear severity labels, change sizing, verification checks, and honest decision-making.
  • Use Case: A pull request from a human or another agent can be reviewed against the spec, tested changes, and project conventions before approval.

Quick Start

Use this skill to review the latest code change and return clear findings with severity labels, verification notes, and a final approval 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 review a pull request for correctness, security, and performance before merge?

To review a pull request effectively, evaluate code changes across correctness, readability, architecture, security, and performance. This multi-axis code review approach identifies issues beyond passing tests, applying severity labels and verification checks to ensure merge readiness.

What is the best way to review AI-generated code changes before approving them?

The best way to review AI-generated code is to treat it like human-authored changes. Review the implementation against project conventions and specifications, checking for dead-code hygiene, architectural flaws, and security vulnerabilities before providing a final approval verdict.

Can I review refactored code without integrating external code quality tooling?

Yes, you can review refactored code without external tooling. This approach applies internal review discipline to assess changes, offering change sizing guidance and severity-labeled findings to evaluate refactors independently of third-party analysis platforms.

How do I label severity and size for code review findings on bug fixes?

To label severity and size for bug fix reviews, apply structured review discipline. Categorize findings by impact severity, provide change sizing guidance to keep diffs manageable, and run verification checks to confirm the bug fix resolves the issue.

Does this code review process support identifying dead code and architecture issues?

Yes, the code review process explicitly supports dead-code hygiene and architecture analysis. It evaluates changes across five dimensions, ensuring that refactors and bug fixes maintain structural integrity and remove unused code paths before returning a verdict.