harsh-critic

Name: harsh-critic
Availability: InStock
Author: Zivtech

Reviews code, plans, and analysis using a structured multi-perspective protocol with evidence-backed findings.

1|Updated Mar 2, 2026

Search Tags:#code review #evidence-based #plan review #analysis review #structured review

Ready to run

npx skills add https://github.com/zivtech/harsh-critic --skill harsh-critic

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: harsh-critic
Source: https://github.com/zivtech/harsh-critic/tree/main/.agents/skills/harsh-critic
Command: npx skills add https://github.com/zivtech/harsh-critic --skill harsh-critic

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

Harsh Critic solves the problem of inadequate reviews that often miss gaps in code, plans, and analysis by providing a thorough, structured, and evidence-backed review process.

Core Features & Use Cases

Thorough Review: Utilizes a 5-phase protocol to ensure comprehensive coverage of the review subject.
Multi-Perspective: Reviews from various angles such as security, new-hire, ops, executor, stakeholder, and skeptic.
Evidence-Driven: Ensures every critical finding includes evidence to back it up.
Calibration Guidance: Provides a framework to avoid over-aggressive or rubber-stamp reviews.
Use Case: For developers looking to conduct a detailed review of their codebase before deployment or for project managers seeking a critical assessment of their project plans.

Quick Start

To perform a harsh review of a code file, use the command: /harsh-critic /path/to/code/file.

Frequently Asked Questions about harsh-critic

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

FAQPage Schema

How do I conduct an evidence-based code review to find missing test cases?▼

An evidence-based code review ensures every critical finding is backed by proof through a structured 5-phase protocol. It uncovers missing cases by examining the subject from multiple perspectives like security, ops, and stakeholder.

What is an adversarial plan review and when do I need it?▼

An adversarial plan review critically evaluates project plans to uncover weak reasoning and missing cases. You need it before deployment or major milestones to ensure thorough examination and evidence-backed validation.

How do I perform a structured review of my codebase before deployment?▼

Perform a structured review by executing a 5-phase protocol that examines the codebase from multiple perspectives. This process ensures thorough coverage and requires evidence for every critical finding to avoid inadequate assessments.

Can I use a multi-perspective analysis to review project plans and documentation?▼

Yes, multi-perspective analysis reviews project plans by evaluating them from security, new-hire, ops, executor, stakeholder, and skeptic angles. This approach ensures comprehensive coverage and evidence-driven findings for weak reasoning.

How do I avoid rubber-stamp or over-aggressive reviews during code analysis?▼

Avoid rubber-stamp or over-aggressive reviews by using calibration guidance within a structured review protocol. This framework enforces evidence requirements for every finding, ensuring balanced and objective critical assessments.