skills.rest
reddb-io
reddb-ioOFFICIAL
Explore all skills by this author →
GitHub

verify

Verify code changes by driving a live app via CDP and checking ground-truth snapshots.

20|2|Updated May 16, 2026
Search Tags:#web app#manual testing#chrome devtools#cdp#verify#snapshot#accessibility tree
One-click install
npx skills add https://github.com/reddb-io/red-skills --skill verify-reddb-io
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: verify
Source: https://github.com/reddb-io/red-skills/tree/main/plugins/dev/skills/engineering/verify
Command: npx skills add https://github.com/reddb-io/red-skills --skill verify-reddb-io

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? It prevents unverified claims about UI behavior by requiring every assertion about a code change to be backed by a fresh accessibility-tree snapshot from a live running app, eliminating hallucinated confirmations before closing issues or approving PRs. ## Core Features & Use Cases - Live App Verification: Launch the project's dev server and drive Chrome through the DevTools Protocol to inspect real rendered state. - Ground-Truth Snapshots: Capture accessibility trees, console logs, and network responses via red-browser snapshot to confirm buttons, headings, API calls, and error-free consoles. - Stale-Ref Discipline: Re-snapshot after every navigation or state change so node references are never reused across page reloads. - Use Case: When asked to confirm a bug fix works, start the app, open Chrome with --remote-debugging-port=9222, take a snapshot, and paste the relevant JSON excerpt proving the fixed element renders before closing the issue. ## Quick Start Ask the agent to verify that the recent fix works by running the app and checking a red-browser snapshot of the page.

Frequently Asked Questions about verify

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

FAQPage Schema
How do I verify a UI fix works before closing an issue?▼

Start the app's dev server, launch Chrome with --remote-debugging-port=9222, then run red-browser snapshot to capture the accessibility tree. Confirm the expected element exists in the a11y output and paste the JSON excerpt as evidence before closing.

How to check for console errors in a running web app?▼

Take a red-browser snapshot against the CDP endpoint and inspect the console array in the JSON output. Any entry with level "error" indicates a console error emitted since the driver connected.

Does red-browser snapshot work with headless Chrome in CI?▼

Yes, launch Chrome with --headless=new, --remote-debugging-port=9222, and --no-sandbox for CI or display-less environments. Chromium and Microsoft Edge work as drop-in replacements for google-chrome.

Why do node refs become stale after page navigation?▼

A ref from a snapshot taken before a reload, navigation, or state change may point to a node that no longer exists. Always re-snapshot and re-resolve refs after any meaningful interaction before asserting on visible state.

When is a snapshot required instead of saying tests pass?▼

A snapshot is required whenever the task is visual or interactive, such as confirming a button renders or a dialog opens. Declaring "LGTM" or citing test results is not a substitute for ground-truth evidence from the live app.

Related Skills

Explore More Software Engineering Skills→
Andreicr1Andreicr1

ce:polish-beta

Boot a feature's dev server and open it in the browser.

Community
Advanced
missingbulbmissingbulb

merge-to-main

Merges the current branch or pull request into main using squash merge via GitHub.

Community
Intermediate
mohitmishra786mohitmishra786

test

Generate unit, integration, and end-to-end tests with Pytest, Jest, Playwright, and k6.

Community
Advanced
TheCardGoatTheCardGoat
14

playwright-cli

Automate browser UI interactions via a Playwright-driven CLI.

Official
Advanced