code-review-workflow

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

Updated Dec 13, 2025

Search Tags:#architecture #checklist #security #static-analysis #quality-assurance #code-review

Ready to run

npx skills add https://github.com/imehr/vet --skill code-review-workflow

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: code-review-workflow
Source: https://github.com/imehr/vet/tree/main/.claude/skills/code-review-workflow
Command: npx skills add https://github.com/imehr/vet --skill code-review-workflow

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a structured, repeatable review process that acts as the final gate before production, ensuring maintainability, security, and design integrity.

Core Features & Use Cases

Architecture & Design checks to enforce layer boundaries and SRP.
Correctness & Security evaluation with checks for edge cases, race conditions, input validation, auth, and secrets handling.
Review etiquette guidance and actionable feedback, driven by a centralized checklist and security practices.
Use Case: Before merging a PR, the Skill analyzes the changes, flags design violations, security gaps, and potential performance issues, and provides concrete remediation suggestions.

Quick Start

Activate this skill in Claude Code and run a code review on the current PR to surface architecture, security, and maintainability issues.

Frequently Asked Questions about code-review-workflow

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

FAQPage Schema

How do I structure a code review for security and architecture issues?▼

Structure your code review using a checklist-driven approach that evaluates architecture, correctness, and security separately. This method enforces layer boundaries, checks for edge cases, and applies OWASP-inspired practices to ensure safe deployment and maintainability.

What should a pull request review cover before merging to production?▼

A pull request review should cover design violations, security gaps like input validation and secrets handling, race conditions, and performance issues. Applying a centralized checklist ensures maintainability and design integrity before merging to production.

Can I use a single code review process for both frontend and backend stacks?▼

Yes, a structured review process can be applied across frontend and backend stacks. By using a repeatable checklist for architecture, correctness, and security, you can surface design violations and potential security gaps regardless of the specific technology stack.

How do I check for security gaps and edge cases during a code audit?▼

Check for security gaps and edge cases during a code audit by adhering to OWASP-inspired practices. Focus on input validation, authentication, race conditions, and secrets handling to identify potential vulnerabilities and provide concrete remediation suggestions.

What is the best way to enforce Single Responsibility Principle in code reviews?▼

The best way to enforce the Single Responsibility Principle (SRP) in code reviews is through dedicated architecture and design checks. These checks verify layer boundaries and ensure each component has a single reason to change, improving overall maintainability.