skills.rest
STUkh
STUkhCOMMUNITY
Explore all skills by this author →
GitHub

sparq:validate

Detect drift between E2E tests and current UI, codebase, and design artifacts.

27|4|Updated Feb 27, 2026
Search Tags:#automation#e2e#validation#qa#validate#test-maintenance#ui-drift
One-click install
npx skills add https://github.com/STUkh/sparq-assistant --skill sparq-validate
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: sparq:validate
Source: https://github.com/STUkh/sparq-assistant/tree/main/claude/skills/sparq-validate
Command: npx skills add https://github.com/STUkh/sparq-assistant --skill sparq-validate

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Validating existing E2E tests to ensure they remain aligned with the current UI, design references, and codebase, reducing flaky failures caused by drift.

Core Features & Use Cases

  • Scan E2E test files to extract selectors, URLs, and flow steps.
  • Compare test expectations against the live UI, component library updates, and code structure.
  • Generate a structured validation report with actionable fixes for drift, broken selectors, and stale assertions.

Quick Start

Run sparq:validate e2e/ to start drift analysis on your E2E tests.

Frequently Asked Questions about sparq:validate

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

FAQPage Schema
How do I detect UI drift in my E2E tests after a component library update?▼

To detect E2E test drift after component library updates, scan test files to extract selectors and flow steps, then compare them against the live UI and codebase to identify broken selectors and generate actionable validation reports.

Why are my E2E tests failing after recent UI changes, and how do I validate them?▼

E2E tests fail after UI changes due to drift between test expectations and the updated interface; validate them by comparing test selectors, URLs, and assertions against current design artifacts and code structure to pinpoint stale references.

What is the best way to check for broken selectors in E2E test suites?▼

The best way to check for broken selectors in E2E test suites is running automated drift analysis that compares extracted selectors against the live UI and codebase, providing a structured report with specific fixes for outdated references.

Can I run automated health checks on existing E2E tests against the current codebase?▼

Yes, you can run automated periodic health checks on existing E2E tests by scanning test files for selectors, URLs, and assertions, then validating them against the current codebase and design artifacts to catch drift and flaky failures.

Does E2E test validation work with web apps that have frequent design updates?▼

E2E test validation works effectively with web apps experiencing frequent design updates by comparing extracted test flows and assertions against live UI changes, ensuring tests remain aligned with current design references and reducing flaky failures.

What limitations exist when validating E2E tests against design artifacts?▼

Validation limitations depend on the alignment between test files and design artifacts; the process extracts selectors and flows from existing tests, so incomplete or outdated test suites may yield less actionable drift reports.

Related Skills

Explore More Software Engineering Skills→
zhizhunbaozhizhunbao

senior-qa

Generate Jest, React Testing Library, and Playwright tests for React/Next.js projects.

Community
Advanced
yoshisadayoshisada

kiln-qa-audit

Scan test files across Playwright, Vitest, Jest, Mocha, and PyTest to identify duplicate scenarios and generate a Markdown audit report.

Community
Advanced
kimjuyoung1127kimjuyoung1127

labeling-feature-add

Integrate modular annotation features into the labeling workspace dashboard workflow.

Community
Advanced
imonmiimonmi

qa-only

Test a web application and produce a structured QA report with evidence and repro steps.

Community
Intermediate