skills.rest
YitzhakPeleg
YitzhakPelegCOMMUNITY
Explore all skills by this author →
GitHub

critical-reviewer

Identify actionable issues in code reviews using a three-phase workflow.

Updated Dec 30, 2025
Search Tags:#quality-assurance#code-review#pull-request#review-process#critical-review#engineering-quality
One-click install
npx skills add https://github.com/YitzhakPeleg/claude-code-config --skill critical-reviewer
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: critical-reviewer
Source: https://github.com/YitzhakPeleg/claude-code-config/tree/main/skills/critical-reviewer
Command: npx skills add https://github.com/YitzhakPeleg/claude-code-config --skill critical-reviewer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Existing code review processes often miss critical issues or fail to provide actionable feedback, leading to unstable releases and wasted time.

Core Features & Use Cases

  • Structured guidance: Follow a consistent three-phase workflow (context analysis, issue discovery, formatted feedback) to surface meaningful improvements.
  • Quality gate: Enforces minimum findings per review to prevent approvals with shallow feedback.
  • Educational value: Scaffolds reviewers to articulate risks, patterns, and best practices for broader engineering improvement.

Quick Start

Review a new PR and apply the three-phase workflow to generate actionable, formatted feedback.

Frequently Asked Questions about critical-reviewer

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

FAQPage Schema
How do I ensure my code review feedback is actionable and catches critical issues?▼

Actionable code review feedback requires a structured workflow that enforces minimum findings and standardized comment formats. This ensures reviewers analyze context, discover issues, and provide thorough feedback rather than shallow approvals.

What is the best way to structure a pull request review process?▼

The best way to structure a pull request review process is through a three-phase workflow: context analysis, issue discovery, and formatted feedback. This structured approach surfaces meaningful improvements and prevents approvals with shallow feedback.

Why does my code review process miss critical issues before merging?▼

Code review processes miss critical issues when they lack structured guidance and minimum findings requirements. Without enforcing thorough issue discovery and standardized feedback, reviewers fail to provide actionable feedback, leading to unstable releases.

Can I enforce minimum code review findings to prevent shallow approvals?▼

Yes, you can enforce minimum code review findings through a structured quality gate. This approach scaffolds reviewers to articulate risks, patterns, and best practices, preventing shallow approvals and ensuring thorough, high-quality feedback.

How do I format code review comments for consistent engineering quality?▼

Format code review comments using a standardized format within a structured three-phase workflow. This ensures consistent approvals by guiding reviewers through context analysis, issue discovery, and formatted feedback across software projects.

Related Skills

Explore More Software Engineering Skills→
nillenille

Code Review

Review code diffs for correctness, security, and conventions.

Community
Advanced
basilebongbasilebong
1

pr-comment-analyzer

Classify GitHub or GitLab review comments as actionable, non-actionable, or ambiguous.

Community
Advanced
IndustrialIndustrial

code-reviewer

Analyze code for security vulnerabilities and performance issues.

Community
Advanced
LISANG3LISANG3
1

requesting-code-review

Analyzes code changes between Git commits using a subagent reviewer.

Community
Intermediate