review-hard

Reviews task code changes for correctness, safety, and maintainability risks before closure or PR prep.

6|Updated Jul 10, 2026
One-click install
npx skills add https://github.com/Mozurok/fhorja.dev --skill review-hard-mozurok
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: review-hard
Source: https://github.com/Mozurok/fhorja.dev/tree/main/.claude/skills/review-hard
Command: npx skills add https://github.com/Mozurok/fhorja.dev --skill review-hard-mozurok

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? AI-assisted coding sessions produce changes that are easy to close without a rigorous risk check, letting correctness bugs, unsafe assumptions, and hidden regressions slip into PRs. This Skill performs a skeptical senior-engineer review of the current task's changes and recommends the smallest safe next step. ## Core Features & Use Cases - Risk-ranked findings: Classifies issues as must-fix, should-fix, or optional, each tagged with impact and effort bands and ordered by value. - No-op discipline: Returns an explicit no-op when the diff and validation evidence are unchanged since the last meaningful review, avoiding review churn. - Optional consensus mode: Supports --consistency N to run N independent review passes merged by consensus, plus a refuter stage that attempts to disprove surviving findings. - Use Case: After completing an implementation slice in a Fhorja task, run the review before slice closure or PR packaging to surface contract mismatches, weak tests, and over-engineering, then route the findings to the right follow-up command. ## Quick Start Ask the assistant to run review-hard on the active task to check the current changes for real engineering risks before closing the slice.

Frequently Asked Questions about review-hard

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

FAQPage Schema
How do I review code changes before closing a task slice?▼

Run review-hard on the active task after an implementation slice completes. It reads the task state, decisions, plan, and actual code changes, then returns must-fix and should-fix findings ranked by impact, plus a recommended next command.

What is the difference between review-hard and a full external code review?▼

review-hard is a focused internal pre-PR engineering risk check, not a replacement for external review systems. It surfaces meaningful correctness, safety, and maintainability issues and deliberately skips cosmetic feedback.

When should I use the --consistency N mode?▼

Use --consistency N only for high-stakes changes where extra confidence justifies the multiplied cost. It runs N independent review passes, merges findings by consensus, and applies a refuter stage that tries to disprove each surviving finding; N=3 is recommended.

Why does review-hard sometimes return a no-op?▼

It returns a no-op when the diff and validation evidence are unchanged since the last meaningful review, so re-reviewing would not materially change conclusions. It still emits a short NO_OP trace for auditability instead of rewriting task state.

Can review-hard handle pasted runtime logs or crash traces?▼

No. Runtime-debug payloads such as logcat dumps or stack traces are routed to incident-triage before any review work begins. Mixed payloads are split: code-risk parts are reviewed here and debug parts are routed onward.