shared-review-workflow

Define severity levels, approval gates, and fix constraints for review workflows.

3|1|Updated Feb 12, 2026

Search Tags:#quality #governance #review #approval #gate #severity #fixes

Ready to run

npx skills add https://github.com/edfenton/claude-skills --skill shared-review-workflow

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Severity definitions, approval gate protocol, and fix constraints shared across all review and test skills across platforms.

Core Features & Use Cases

Define severity levels: must-fix, should-fix, nice-to-have for consistent risk assessment.
Enforce an approval gate: require approvals before merging and deploying fixes.
Enforce fix constraints: avoid introducing dependencies and ensure tests remain green.

Quick Start

Apply this workflow to a failing change by categorizing issues, triggering approvals, and documenting fixes.

Frequently Asked Questions about shared-review-workflow

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

FAQPage Schema

How do I standardize code review severity levels across different platforms?▼

Standardize review severity by defining consistent must-fix, should-fix, and nice-to-have categories. This shared workflow applies these severity levels across code, design, and unit-test reviews to ensure consistent risk assessment and gating across all platforms.

How do I enforce an approval gate for CI/CD deployments?▼

Enforce an approval gate in CI/CD by requiring explicit approvals before merging changes or deploying fixes. This workflow establishes a strict governance protocol to prevent risky changes and ensure safe, auditable, and traceable deployments.

What are the fix constraints for preventing risky changes during code reviews?▼

Fix constraints for preventing risky changes include avoiding the introduction of new dependencies and ensuring tests remain green. These fixed constraints standardize remediation workflows and prevent unsafe modifications in CI/CD environments.

How does a shared review workflow handle traceable decision-making?▼

A shared review workflow handles traceable decision-making by categorizing issues into severity levels, triggering mandatory approvals, and documenting remediation. This satisfies strict governance requirements for safe, auditable changes in CI/CD environments.

Can I apply the same severity gates to both design reviews and unit tests?▼

Yes, you can apply the same severity gates to design reviews and unit tests. This workflow defines shared severity levels and fix constraints that enable consistent gating and remediation workflows across code-review, design-review, and unit-test skills.

When do I need a standardized review workflow with severity gates?▼

You need a standardized review workflow with severity gates when you require strict governance, traceable decision-making, and safe, auditable changes in CI/CD environments. It prevents risky changes by enforcing approvals and fixed remediation constraints.