Visual verification

Skill gruckion/marathon-ralph/skills/visual-verification

Visually verify implemented features work correctly before marking complete. Use when testing UI changes, verifying web features, or checking user flows work in the browser.From its SKILL.md

Install

npx -y skills add gruckion/marathon-ralph --skill visual-verification

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
18 stars18 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

1.3 KB, as published. Nobody here has run it

Visual Verification

Verify implemented features work correctly through actual user interaction, not just automated tests.

When to Use

After implementing any UI feature
Before marking an issue as complete
When acceptance criteria involve user-visible behavior
After fixing UI bugs

Approaches

Web Applications: See browser-verification.md for Playwright MCP workflow.

Mobile Applications: See mobile-verification.md (Coming soon)

Verification Checklist

Before marking any UI task complete:

Dev server is running and accessible
Feature renders without console errors
Elements render correctly and do not incorrectly overlap
User interactions work as expected
Edge cases handled (empty states, loading, errors)
Screenshot captured as evidence

What NOT to Do

Skip visual verification because "tests pass"
Mark issues complete without browser testing
Assume dev mode catches all errors (run npm run build too)
Test only happy paths