What problem does it solve? AI coding agents frequently hallucinate file paths and APIs, claim work is done without running tests, drift beyond the requested scope, or stop mid-task and ask for permission to continue. This Skill provides behavioral guardrails that prevent these failure modes during code changes. ## Core Features & Use Cases - Verification rules: Requires reading files before editing, running tests or linters after changes, and reviewing diffs before declaring completion. - Hallucination prevention: Mandates grounding proposals in inspected source code, marking claims as read or assumed, and stating uncertainty explicitly. - Scope and persistence discipline: Enforces one logical change at a time, the Two-Reading Rule for ambiguous requirements, and continuing multi-step tasks until a true blocker is hit. - Use Case: An engineer agent implementing a multi-phase spec uses these rules to verify each change with the test suite, avoid silently reclassifying acceptance criteria, and produce a Completion Ledger accounting for every item. ## Quick Start Load the agent-reliability skill so the agent verifies every code change with tests and stays within the requested scope.
