review

Enforce traceable, evidence-based findings with confidence labels and falsification checks.

5|Updated Mar 10, 2026
One-click install
npx skills add https://github.com/humblemuzzu/ghosttyyy --skill review-humblemuzzu
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: review
Source: https://github.com/humblemuzzu/ghosttyyy/tree/main/pi-setup/config-skills/review
Command: npx skills add https://github.com/humblemuzzu/ghosttyyy --skill review-humblemuzzu

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Epistemic standards for evaluation and analysis are critical to producing defensible findings. This skill provides a structured approach to load before reviewing code, debugging, reporting findings, or any task where claims must be defensible and traceable.

Core Features & Use Cases

  • Traceability and evidence-based reasoning: enforces trace-or-delete, requiring links to code, logs, or data.
  • Confidence labeling: denote VERIFIED, HUNCH, or QUESTION for claims.
  • Falsification mindset: design tests to disprove hypotheses before confirming.
  • Clear reporting: aligns with quality criteria and standardized findings format.

Quick Start

Load this skill before reviewing code, debugging, or reporting findings to ensure every claim is traceable and defensible.

Frequently Asked Questions about review

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

FAQPage Schema
How do I ensure code review findings are traceable and evidence-based?

To ensure code review findings are traceable, load this skill before evaluation to enforce a trace-or-delete rule, requiring every claim to link directly to code, logs, or data.

What is the best way to label confidence levels during a debugging audit?

Labeling confidence during a debugging audit involves marking claims as VERIFIED, HUNCH, or QUESTION, which provides clear epistemic standards for analytical reporting and hypothesis tracking.

How do I apply falsification checks when reviewing analytical reports?

Applying falsification checks during analytical reporting requires designing tests specifically to disprove your hypotheses before confirming them, ensuring defensible and evidence-based findings.

Can I use this evaluation skill for general debugging tasks without dependencies?

Yes, you can use this evaluation skill for debugging tasks without dependencies, as it provides a structured reasoning approach for audits and analytical reporting requiring traceable evidence.

When do I need explicit traceability standards for evaluation tasks?

You need explicit traceability standards for evaluation tasks when claims must be defensible, such as during code reviews, debugging, or audits where evidence-based reasoning is critical.

Does evidence-based code review work without falsification testing?

Evidence-based code review without falsification testing lacks epistemic rigor; designing tests to disprove hypotheses before confirming them is required to produce defensible and traceable findings.