reality-check

Name: reality-check
Availability: InStock
Author: aviz85

Analyze codebases to surface misleading tests, mocks, and health checks.

45|13|Updated Jan 6, 2026

Search Tags:#security #error-handling #health-check #code-audit #technical-debt #test-quality #mock-abuse

Ready to run

npx skills add https://github.com/aviz85/claude-skills-library --skill reality-check-aviz85

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: reality-check
Source: https://github.com/aviz85/claude-skills-library/tree/main/plugins/reality-check/skills/reality-check
Command: npx skills add https://github.com/aviz85/claude-skills-library --skill reality-check-aviz85

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Deep, no-nonsense code audits that reveal misleading patterns, false confidence in tests, mocks, and health checks, and hidden debt.

Core Features & Use Cases

Systematic detection across mocks, fake implementations, broken error handling, meaningless tests, and hidden debt.
Generates a structured Reality Check Report with actionable recommendations for remediation.
Suitable for code audits, pre-release reviews, and reliability assessments to improve software honesty.

Quick Start

Run the reality-check skill on your project root to generate a structured audit report detailing findings and recommended fixes.

Frequently Asked Questions about reality-check

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

FAQPage Schema

How do I run a code audit to find misleading tests and mock abuse?▼

A code audit for false confidence surfaces misleading tests, mock abuse, and broken error handling by analyzing your codebase to generate a structured report with actionable recommendations for remediation.

What is false confidence in software testing and how does mock abuse hide bugs?▼

False confidence in software testing occurs when fake implementations and mocks pass tests without validating real behavior, creating hidden risks that a thorough code audit exposes by evaluating test quality and mock usage patterns.

How do I check my CI pipeline for hidden technical debt and broken error handling?▼

You can check your CI pipeline for hidden technical debt and broken error handling by running a systematic reliability assessment across your project, which outputs a structured report detailing TODOs, error handling flaws, and technical debt findings.

Can I use this reliability assessment for pre-release reviews across different programming languages?▼

Yes, this reliability assessment is applicable for pre-release reviews across projects, languages, and CI pipelines, systematically detecting meaningless tests, fake implementations, and hidden debt to ensure software honesty before deployment.

What is the best way to identify meaningless health checks in a codebase?▼

The best way to identify meaningless health checks in a codebase is to perform a systematic code audit that surfaces false confidence patterns, evaluating health check implementations alongside mock usage and test quality to output a structured remediation report.

When should I perform a technical debt and test quality assessment before release?▼

You should perform a technical debt and test quality assessment during code audits and pre-release reviews to surface hidden risks, TODOs, and misleading tests, ensuring your reliability assessment produces actionable remediation recommendations.