review-hard

Review a specified codebase area for bugs, regressions, and unsafe assumptions.

3|Updated Apr 6, 2026
One-click install
npx skills add https://github.com/X0x888/oh-my-claude --skill review-hard
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: review-hard
Source: https://github.com/X0x888/oh-my-claude/tree/main/bundle/dot-claude/skills/review-hard
Command: npx skills add https://github.com/X0x888/oh-my-claude --skill review-hard

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill unit addresses the challenge of finalizing code changes without thorough review, potentially leading to broken code or missed issues.

Core Features & Use Cases

  • Findings-First Review: Focuses on identifying bugs, regressions, and unsafe assumptions before code is finalized.
  • No Editing: Ensures the reviewer's role is to identify issues without modifying files.
  • Optional Focus: Allows specifying a focused area of the codebase for review.
  • Agent-Based: Utilizes a quality-reviewer agent to perform the review.

Quick Start

Run the review-hard skill on your latest changes by typing: /review-hard

Frequently Asked Questions about review-hard

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

FAQPage Schema
How do I perform a thorough code review to catch bugs and regressions before finalizing changes?

A thorough code review identifies bugs, regressions, and unsafe assumptions before code is finalized. Using an agent-based quality reviewer focuses on finding these issues early in the development cycle without modifying any files.

What is a findings-first code review and how does it improve code quality?

A findings-first code review prioritizes identifying bugs and unsafe assumptions over directly editing files. This approach improves code quality by ensuring the reviewer's role remains strictly to detect issues rather than implement fixes.

Can I target a specific area of the codebase for code review?

Yes, you can specify a focused area of the codebase for code review. This optional targeting allows the quality-reviewer agent to perform a detailed analysis on specific directories or recent changes.

Does this code review tool modify my source files during issue detection?

No, this code review tool does not modify your source files during issue detection. It ensures the reviewer's role is strictly to identify bugs and unsafe assumptions, leaving all code editing to the developer.

What is the best way to detect unsafe assumptions in my code before deployment?

The best way to detect unsafe assumptions is to run an agent-based code review focused on findings. This process highlights potential regressions and logic flaws early in the development cycle before finalizing work.