verification-validator

Validate code changes with pytest, webpack, or Playwright tests based on change type.

Updated Jan 30, 2026
One-click install
npx skills add https://github.com/GoBeromsu/My-Awesome-RA --skill verification-validator
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: verification-validator
Source: https://github.com/GoBeromsu/My-Awesome-RA/tree/main/.claude/skills/verification-validator
Command: npx skills add https://github.com/GoBeromsu/My-Awesome-RA --skill verification-validator

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Validate changes using minimal, change-type based tests.

Core Features & Use Cases

  • Dedicated verification strategies for backend (pytest), frontend (webpack), and full-flow (Playwright).
  • Decision-tree driven selection of tests to minimize run time while preserving confidence.
  • Use case: when only API code changes, run pytest; when only UI files change, run webpack checks; when both change, run full Playwright flows.

Quick Start

Run the verification validator on the updated components to ensure targeted tests pass.

Frequently Asked Questions about verification-validator

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

FAQPage Schema
How do I run minimal verification tests for backend API changes?

Targeted verification for backend API changes uses pytest to validate only the modified components. This decision-tree driven strategy minimizes run time while preserving confidence that the API logic remains intact.

What is the best way to verify frontend component updates without running all tests?

The best way to verify frontend component updates is using webpack checks on the changed UI files. This change-type based strategy isolates frontend verification to keep test execution fast and focused.

When do I need to run full Playwright flows for code modifications?

You need full Playwright flows for code modifications when both backend API and frontend UI files change in the same update. This full-stack verification ensures the entire interaction path remains stable across the modified layers.

Can I use change-type based testing to speed up my CI pipeline?

Yes, you can use change-type based testing to speed up your CI pipeline by directing which tests to run for each scenario. Running only relevant pytest, webpack, or Playwright checks minimizes run time while maintaining confidence.

Does this verification approach support full-stack modifications?

This verification approach supports full-stack modifications by coordinating tests through a simple decision tree. It applies dedicated strategies using pytest for backend, webpack for frontend, and Playwright for full-flow integration.