Skip to content
cccskills
FreePublished on GitHub

reality-verification

This skill should be used when the user asks to "verify a fix", "reproduce failure", "diagnose issue", "check BEFORE/AFTER state", "VF task", "reality check", "check test quality", "mock-only tests", or needs guidance on verifying fixes by reproducing failures before and after implementation, or detecting mock-heavy test anti-patterns.

The English summary is being prepared. Showing the original description.

tzachbon/smart-ralph
Works withPlaywright
See how to install

Files included (3)

  • SKILL.md3.4 KB
  • references/goal-detection-patterns.md2.3 KB
  • references/mock-quality-checks.md3.4 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

Reality Verification

For fix goals: reproduce the failure BEFORE work, verify resolution AFTER.

Goal Detection

Classify user goals to determine if diagnosis is needed. See references/goal-detection-patterns.md for detailed patterns.

Quick reference:

  • Fix indicators: fix, repair, resolve, debug, patch, broken, failing, error, bug
  • Add indicators: add, create, build, implement, new
  • Conflict resolution: If both present, treat as Fix

Command Mapping

Goal KeywordsReproduction Command
CI, pipelinegh run view --log-failed
test, testsproject test command
type, typescriptpnpm check-types or tsc --noEmit
lintpnpm lint
buildpnpm build
E2E, UIPlaywright MCP browser tools
API, endpointWebFetch tool

For E2E/deployment verification, use MCP tools (Playwright MCP browser tools for UI, WebFetch tool for APIs).

BEFORE/AFTER Documentation

BEFORE State (Diagnosis)

Document in .progress.md under ## Reality Check (BEFORE):

## Reality Check (BEFORE)

**Goal type**: Fix
**Reproduction command**: `pnpm test`
**Failure observed**: Yes
**Output**:

FAIL src/auth.test.ts Expected: 200 Received: 401

**Timestamp**: 2026-01-16T10:30:00Z

AFTER State (Verification)

Document in .progress.md under ## Reality Check (AFTER):

## Reality Check (AFTER)

**Command**: `pnpm test`
**Result**: PASS
**Output**:

PASS src/auth.test.ts All tests passed

**Comparison**: BEFORE failed with 401, AFTER passes
**Verified**: Issue resolved

VF Task Format

Add as task 4.3 (after PR creation) for fix-type specs:

- [ ] 4.3 VF: Verify original issue resolved
  - **Do**:
    1. Read BEFORE state from .progress.md
    2. Re-run reproduction command: `<command>`
    3. Compare output with BEFORE state
    4. Document AFTER state in .progress.md
  - **Verify**: `grep -q "Verified: Issue resolved" ./specs/<name>/.progress.md`
  - **Done when**: AFTER shows issue resolved, documented in .progress.md
  - **Commit**: `chore(<name>): verify fix resolves original issue`

Test Quality Checks

When verifying test-related fixes, check for mock-only test anti-patterns. See references/mock-quality-checks.md for detailed patterns.

Quick reference red flags:

  • Mock declarations > 3x real assertions
  • Missing import of actual module under test
  • All assertions are mock interaction checks (toHaveBeenCalled)
  • No integration tests
  • Missing mock cleanup (afterEach)

Why This Matters

WithoutWith
"Fix CI" spec completes but CI still redCI verified green before merge
Tests "fixed" but original failure unknownBefore/after comparison proves fix
Silent regressionsExplicit failure reproduction
Manual verification requiredAutomated verification in workflow
Tests pass but only test mocksTests verify real behavior, not mock behavior
False sense of security from green testsConfidence that tests catch real bugs

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

Command Development

Free

This skill should be used when the user asks to "create a slash command", "add a command", "write a custom command", "define command arguments", "use command frontmatter", "organize commands", "create command with file references", "interactive command", "use AskUserQuestion in command", or needs guidance on slash command structure, YAML frontmatter fields, dynamic arguments, bash execution in commands, user interaction patterns, or command development best practices for Claude Code.

The English summary is being prepared. Showing the original description.

tzachbon/smart-ralph559Updated Sep 16, 2026

communication-style

Free

Output rules for all agents - concise, scannable, actionable. Based on Matt Pocock's planning principles.

The English summary is being prepared. Showing the original description.

tzachbon/smart-ralph559Updated Sep 16, 2026

communication-style

Free

This skill should be used when generating spec artifacts (research.md, requirements.md, design.md, tasks.md), formatting agent output, structuring phase results, or when any Ralph agent needs guidance on concise, scannable output formatting. Applies to all Ralph spec phase agents.

The English summary is being prepared. Showing the original description.

tzachbon/smart-ralph559Updated Sep 16, 2026

delegation-principle

Free

Core principle that the main agent is a coordinator, not an implementer. All work must be delegated to subagents.

The English summary is being prepared. Showing the original description.

tzachbon/smart-ralph559Updated Sep 16, 2026

Hook Development

Free

This skill should be used when the user asks to "create a hook", "add a PreToolUse/PostToolUse/Stop hook", "validate tool use", "implement prompt-based hooks", "use ${CLAUDE_PLUGIN_ROOT}", "set up event-driven automation", "block dangerous commands", or mentions hook events (PreToolUse, PostToolUse, Stop, SubagentStop, SessionStart, SessionEnd, UserPromptSubmit, PreCompact, Notification). Provides comprehensive guidance for creating and implementing Claude Code plugin hooks with focus on advanced prompt-based hooks API.

The English summary is being prepared. Showing the original description.

tzachbon/smart-ralph559Updated Sep 16, 2026

interview-framework

Free

This skill should be used when a Ralph phase must identify critical user decisions, run a layered grill, persist partial answers, obtain explicit approval, or resume an interrupted phase interview before delegating artifact work.

The English summary is being prepared. Showing the original description.

tzachbon/smart-ralph559Updated Sep 16, 2026

See all skills by tzachbon

Report a problem with this skill