ui-feature-verify

Run linting, tests, build, and Playwright E2E for web UI changes.

Updated Dec 29, 2025
One-click install
npx skills add https://github.com/yu-iskw/dbt-artifacts-parser-ts --skill ui-feature-verify
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ui-feature-verify
Source: https://github.com/yu-iskw/dbt-artifacts-parser-ts/tree/main/.claude/skills/ui-feature-verify
Command: npx skills add https://github.com/yu-iskw/dbt-artifacts-parser-ts --skill ui-feature-verify

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Lightweight verification for UI-only changes to @dbt-tools/web, enabling quick checks without running the full verifier.

Core Features & Use Cases

  • Linting, unit tests, and coverage assessment for web UI changes.
  • Fresh build and Playwright E2E checks to validate UI interactions.
  • Coverage gap reporting to surface UI elements requiring tests.

Quick Start

Run the UI feature verify to perform lint, tests, build, and Playwright E2E for web/UI changes.

Frequently Asked Questions about ui-feature-verify

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

FAQPage Schema
How do I verify UI feature changes in dbt-tools without running the full verifier?

Lightweight UI verification for dbt-tools coordinates linting, unit tests, coverage assessment, fresh builds, and Playwright E2E tests. It provides a quick, cohesive workflow for web UI changes without running the full verifier.

Does UI feature verification include Playwright browser setup and E2E testing?

Yes, UI feature verification includes Playwright browser setup and E2E testing. It coordinates these steps alongside linting, testing, and builds to validate web UI interactions end-to-end.

When should I use lightweight UI verification instead of a full verifier?

Use lightweight UI verification when changes are confined to packages/dbt-tools/web/src/ or packages/dbt-tools/web/e2e/ directories. It provides quick checks when running a full verifier would be overkill for web-only modifications.

How do I check for UI test coverage gaps in dbt-tools web changes?

To check UI test coverage gaps, the verification workflow runs coverage assessment and generates gap reports. This surfaces specific UI elements within @dbt-tools/web that require additional tests.

What steps are involved in the web UI feature verification workflow?

The web UI feature verification workflow coordinates linting, unit tests, coverage threshold checks, fresh builds, Playwright browser setup, and E2E testing as a cohesive, repeatable process for @dbt-tools/web.