sanity-check

Name: sanity-check
Availability: InStock
Author: Elliot

Verify key assumptions before proposing changes in software projects.

60|2|Updated Jan 21, 2026

Search Tags:#debugging #verification #assumptions #code-quality #risk-management #root-cause

Ready to run

npx skills add https://github.com/ElliotJLT/Claude-Skill-Potions --skill sanity-check

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: sanity-check
Source: https://github.com/ElliotJLT/Claude-Skill-Potions/tree/main/skills/sanity-check
Command: npx skills add https://github.com/ElliotJLT/Claude-Skill-Potions --skill sanity-check

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents assumption cascades by requiring explicit verification of key premises before proposing solutions or changes.

Core Features & Use Cases

Assumption cataloging: List and assess each assumption's validity.
Verifications & Reproduction: Guiding checks to confirm existence, behavior, and root cause.
Risk mitigation: Halts progress when a critical assumption is wrong, prompting reassessment.

Quick Start

Identify the claim or behavior you are about to assume.
Verify each key assumption with direct checks (read the code, reproduce, inspect logs).
Stop and reassess if a critical assumption cannot be verified.

Frequently Asked Questions about sanity-check

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

FAQPage Schema

How do I verify assumptions before debugging code?▼

Verification of assumptions prevents incorrect solutions by forcing explicit checks before proposing changes. List each key assumption about the problem, then directly confirm it through code inspection, log review, or reproduction. Stop and reassess if any critical assumption cannot be verified.

What's the best way to avoid cascading errors in code fixes?▼

Assumption cascades compound when unverified premises lead to wrong solutions. Before proposing a fix, catalog assumptions explicitly, verify their validity through direct checks, and halt progress if verification fails. This risk mitigation step catches root causes early.

When should I validate my assumptions about code behavior?▼

Validate assumptions before implementing changes across code understanding, debugging, and architectural decisions. Verification steps confirm existence, behavior, and root cause. This is essential in risk-management workflows where incorrect assumptions cascade into flawed solutions.

Can I use assumption verification for architectural decisions?▼

Yes. Assumption verification applies across debugging, code understanding, and architectural decisions. By explicitly listing premises and requiring verification steps before proposing changes, you ensure architectural choices rest on confirmed facts rather than unexamined assumptions.

What happens if a critical assumption can't be verified?▼

If verification fails, the Skill halts progress and prompts reassessment. This safe stop prevents implementation of solutions built on unverified premises, reducing risk and ensuring you understand the actual problem before coding changes.