Reality Verification FAQs

Question 1

Can it check CI/CD pipeline statuses?

Accepted Answer

Yes, it can map goals related to CI or pipelines to specific commands like 'gh run view' to verify if remote builds are passing or failing.

Question 2

What happens if a failure cannot be reproduced before work starts?

Accepted Answer

If no keyword match is found or the reproduction command doesn't fail, the skill provides a fallback to ask the user for clarification or skip the diagnosis phase if appropriate.

Question 3

How does the skill detect if I am fixing a bug versus adding a feature?

Accepted Answer

The skill uses heuristic pattern matching to scan your goal for keywords like 'fix', 'debug', 'broken', or 'error'. If both fix and add patterns are present, it defaults to a 'Fix' classification to ensure rigorous validation.

Question 4

Where are the verification results stored?

Accepted Answer

Results are documented in a .progress.md file within your project, featuring a 'Reality Check (BEFORE)' section for the failure and a 'Reality Check (AFTER)' section for the resolution.

Question 5

Does this skill work with frontend and backend issues?

Accepted Answer

Yes. It uses MCP Playwright for frontend/UI verification and MCP Fetch for backend/API verification, alongside standard project test commands for unit and integration testing.

Reality Verification

Key Features

Use Cases

Reality Verification

Key Features

Use Cases