code-review-excellence

Automate structured code reviews for quality, maintainability, and architecture issues.

Updated Feb 24, 2026
One-click install
npx skills add https://github.com/brian861105/codex-skills --skill code-review-excellence-brian861105
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-review-excellence
Source: https://github.com/brian861105/codex-skills/tree/main/code-review-excellence
Command: npx skills add https://github.com/brian861105/codex-skills --skill code-review-excellence-brian861105

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Rigorous code review focused on quality, maintainability, and architectural soundness; it helps teams catch design and implementation issues before changes are merged.

Core Features & Use Cases

  • Deterministic context collection using the provided script to anchor reviews in the exact change set
  • Structured evaluation across code quality, technical debt, architecture, and testing criteria
  • Guidance for two-pass reviews (architecture and implementation) to improve outcomes

Quick Start

Run the deterministic review process by executing scripts/collect_review_context.sh to gather context before reviewing changes.

Frequently Asked Questions about code-review-excellence

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

FAQPage Schema
How do I automate code review for pull requests to catch architectural issues?

Automating code review for pull requests involves using scripts to collect deterministic context from staged changes, guiding reviewers through architecture and implementation passes to identify maintainability and design issues before merging.

What is a structured two-pass code review and when do I need it?

A structured two-pass code review evaluates architecture first, then implementation details. It is needed when reviewing branch commits to ensure comprehensive criteria coverage across code quality, technical debt, testing, and safety checks.

How to review staged changes with deterministic context collection?

Review staged changes with deterministic context by executing a collection script that anchors the evaluation in the exact change set, ensuring the reviewer analyzes the precise modifications made in the feature branch.

Can I use review automation for technical debt assessment across feature branches?

Yes, review automation supports technical debt assessment across feature branches by applying structured evaluation criteria to identify quality issues and architectural flaws within the committed changes.

What's the best way to ensure quality assurance in software engineering pull requests?

The best way to ensure quality assurance in pull requests is applying a deterministic review workflow that evaluates code quality, technical debt, architecture, and testing criteria across staged changes before merging.