skills.rest
ForeverWorld
ForeverWorldCOMMUNITY
Explore all skills by this author →
GitHub

reality-verification

Reproduce failures and verify fixes by documenting BEFORE and AFTER states.

Updated Aug 27, 2026
Search Tags:#debugging#e2e#verification#reproduction#ci#tests#mock-quality
One-click install
npx skills add https://github.com/ForeverWorld/curdx-ralph --skill reality-verification-foreverworld
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: reality-verification
Source: https://github.com/ForeverWorld/curdx-ralph/tree/main/skills/reality-verification
Command: npx skills add https://github.com/ForeverWorld/curdx-ralph --skill reality-verification-foreverworld

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Reproducing intermittent or persistent failures and proving that a code change actually resolves the original problem can be slow, undocumented, and error prone. This Skill provides a repeatable BEFORE/AFTER verification process so teams can reproduce failures, run targeted reproduction commands, and record structured verification outcomes to avoid regressions and false positives.

Core Features & Use Cases

  • Failure reproduction mapping: Map goal keywords to appropriate reproduction commands such as gh run view --log-failed for CI, project test command for unit tests, pnpm check-types or tsc --noEmit for typing issues, pnpm lint for lint problems, and MCP tools for E2E or API checks.
  • Before/After documentation: Standardize entries in .progress.md under "Reality Check (BEFORE)" and "Reality Check (AFTER)" to capture reproduction commands, observed outputs, timestamps, and verification verdicts.
  • Test quality validation: Run heuristic checks for mock-heavy or fragile tests and flag mock-quality anti-patterns before marking a fix as verified.
  • Use case example: For a failing auth test, record the failing output and timestamp, rerun tests after the change, compare outputs, perform mock-quality checks, and document verification success or required follow-ups.

Quick Start

Ask the skill to reproduce and verify a reported failing test by providing the spec name, reproduction steps, and target command so it documents BEFORE and AFTER verification.

Frequently Asked Questions about reality-verification

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

FAQPage Schema
How do I verify a code fix actually resolves a failing CI test?▼

Reproduce test failures by mapping goal keywords to reproduction commands like gh run view --log-failed for CI or specific test commands, documenting observed outputs and timestamps in .progress.md.

What is the best way to document before and after states for test reproduction?▼

Document before and after states by recording reproduction commands, observed outputs, timestamps, and verification verdicts under structured Reality Check sections in .progress.md to ensure traceability.

How do I reproduce E2E test failures using CLI or MCP tools?▼

Reproduce E2E test failures by mapping the failing test keywords to appropriate MCP tools or CLI commands, executing them to capture the error output, and logging the results for comparison.

Does this approach work for checking mock-heavy test quality during debugging?▼

Yes, the verification process includes heuristic checks that flag mock-quality anti-patterns in fragile or mock-heavy tests before marking a fix as verified, preventing false positives.

Can I use this to verify API regressions and build errors?▼

Yes, you can verify API regressions and build errors by running targeted reproduction commands such as tsc --noEmit for typing issues or pnpm lint for lint problems, then comparing outputs.

Why do I need to document reproduction commands in .progress.md?▼

Documenting reproduction commands in .progress.md provides a repeatable verification process that avoids regressions by ensuring teams can rerun targeted commands and compare structured BEFORE and AFTER outputs.

Related Skills

Explore More Software Engineering Skills→
ProjectEuropaProjectEuropa
4

e2e-debug

Diagnose failing Playwright E2E tests and CI regressions with repair steps.

Community
Advanced
SjdjdiejdrirhdkjejSjdjdiejdrirhdkjej

regression-test-generator

Generate regression tests from bug reports and detected test frameworks.

Community
Advanced
jrmatherlyjrmatherly
1

precheck

Run backend tests, lint, and frontend type checks before commits.

Community
Intermediate
AbdullahMalik17AbdullahMalik17
9

systematic-debugging

Identify root causes of bugs using a structured four-phase process.

Community
Advanced