Delegate browser verification and site QA to a subagent.
npx skills add https://github.com/apappas57/sinew --skill browser-verify-apappas57
Please help me install this Agent Skill. Skill: browser-verify Source: https://github.com/apappas57/sinew/tree/main/skills/core/browser-verify Command: npx skills add https://github.com/apappas57/sinew --skill browser-verify-apappas57
This Skill verifies deployed websites without polluting the parent conversation with screenshots, browser state, or other bulky QA artifacts.
Use /browser-verify with a URL, client name, or all to delegate a site verification run and receive a plain-text QA summary.
High-intent search queries and answers about installing and using this skill.
Site verification can be delegated to a subagent, keeping screenshots and browser state out of the parent context. You receive a plain-text QA summary instead of bulky artifacts, ensuring your main conversation stays clean and focused.
Batch verification supports checking a single URL, a named client site, or all registered sites in one run. The delegated subagent navigates tabs, reviews console errors, and checks mobile-responsive layouts, returning a consolidated plain-text report.
Automated deployment checks are handled by delegating browser QA to a subagent. This mechanism validates that pages load correctly, navigation works, forms are present, and footer content is accurate, delivering a plain-text reporting summary without polluting the main context.
Yes, this site testing approach requires no extra dependencies. It leverages agent-based delegation to handle tab creation, navigation, and visual QA, generating plain-text reporting summaries directly without needing external component installations.
Subagent delegation isolates browser state and screenshots from the parent context, which standard browser automation often loads directly. This approach ensures your main context remains clean while still performing comprehensive mobile-responsiveness checks and form testing.
A key limitation is the strict reliance on plain-text reporting only. Because screenshots and browser state are intentionally kept out of the parent context, you cannot directly view or interact with the visual artifacts captured during the live-site validation.
stromy-orgGuide clients through website builds with content-only proposals and Azure SWA preview URLs.
cyberpunk042Identify failing deployments and roll back to the last known good state.
4lermanAutomates DevOps workflows including CI/CD pipelines, infrastructure as code, and container deployments with rollback support.
hffmnnjCompare screenshots pixel-by-pixel to detect unintended UI changes.
