← ClaudeAtlas

soleri-verification-before-completionlisted

Triggers: "verify this works", "check output", "quality gate", "run tests before done". Internal quality gate before task completion. Use deliver-and-ship for shipping.
adrozdenko/soleri · ★ 6 · AI & Automation · score 74
Install: claude install-skill adrozdenko/soleri
# Verification Before Completion **Core principle:** Evidence before claims, always. ## The Iron Law ``` NO COMPLETION CLAIMS WITHOUT FRESH VERIFICATION EVIDENCE ``` If you haven't run the verification command in this message, you cannot claim it passes. ## The Gate Function ``` 1. IDENTIFY: What command proves this claim? 2. RUN: Execute the FULL command (fresh, complete) 3. READ: Full output, check exit code, count failures 4. VERIFY: Does output confirm the claim? - NO → State actual status with evidence - YES → State claim WITH evidence 5. AGENT CHECK: Run system diagnostics 6. ONLY THEN: Make the claim ``` ## Check Loop Status If this task is part of a tracked loop: ``` YOUR_AGENT_core op:loop_status ``` Report loop iteration status before claiming completion. ## Agent System Checks After passing verification commands: - `YOUR_AGENT_core op:admin_health` — catches vault corruption, stale caches - `YOUR_AGENT_core op:admin_diagnostic` — module status, database integrity, config validity - `YOUR_AGENT_core op:admin_vault_analytics` — knowledge quality metrics If any check reports problems, address before claiming completion. ## Common Failures | Claim | Requires | Not Sufficient | | ---------------- | ----------------------- | ----------------------------- | | Tests pass | Test output: 0 failures | Previous run, "should pass" | | Build succeeds | Build command: exit 0 | Linter passing