code-review

Name: code-review
Availability: InStock
Author: Ozby

Analyze code changes for security, quality, and maintainability issues during pull requests.

1|Updated Mar 17, 2025

Search Tags:#architecture #security #maintainability #code-quality #code-review #pull-request

Ready to run

npx skills add https://github.com/ozby/node-pubsub --skill code-review-ozby

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: code-review
Source: https://github.com/ozby/node-pubsub/tree/main/.codex/skills/code-review
Command: npx skills add https://github.com/ozby/node-pubsub --skill code-review-ozby

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Conducting comprehensive, consistent, and actionable code reviews that uncover security vulnerabilities, maintainability issues, and quality risks before merging changes.

Core Features & Use Cases

Two-lane review workflow: parallel evaluation of code quality and architectural implications.
Severity-rated feedback: categorize findings as CRITICAL, HIGH, MEDIUM, or LOW with concrete remediation guidance.
Final synthesis & gating: produces a merge verdict with explicit next steps for release decisions.

Quick Start

Review the latest pull request by running the code-review workflow to identify issues across security, quality, and maintainability.

Frequently Asked Questions about code-review

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

FAQPage Schema

What is a structured code review process for pull requests?▼

A structured code review evaluates pull request changes using parallel lanes for code quality and architectural implications. It categorizes security and maintainability findings by severity and synthesizes an explicit merge verdict to gate releases.

How do I automate code reviews to catch security vulnerabilities before merging?▼

Automate code reviews by running a workflow that evaluates code changes for security, quality, and maintainability issues. This produces severity-rated feedback with concrete remediation guidance and a final synthesis to gate merges.

Can I prioritize code review findings by severity for architectural risks?▼

Yes, code review findings are categorized as CRITICAL, HIGH, MEDIUM, or LOW. This severity-based prioritization covers architectural risk synthesis and security vulnerabilities, providing concrete remediation steps for each level.

Does the code review workflow support parallel evaluation of code quality and architecture?▼

Yes, the code review workflow uses a two-lane review process. It conducts parallel evaluation of code quality and architectural implications to provide comprehensive gatekeeping before merges.

What is the best way to generate a merge verdict from code review findings?▼

The best way to generate a merge verdict is through final synthesis and gating. This process aggregates severity-rated feedback from code quality and architectural risk evaluations to produce an explicit merge decision with next steps.

When do I need deterministic scoring for code reviews?▼

Deterministic scoring is needed for collaborative software projects requiring rigorous gatekeeping before merges. It ensures consistent, actionable code reviews that uncover maintainability issues and quality risks across pull requests.