runtime-validation

Validate software features through browser, API, and CLI scenarios.

6|Updated Feb 13, 2026
One-click install
npx skills add https://github.com/damianpapadopoulos/auto-claude-skills --skill runtime-validation-damianpapadopoulos
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: runtime-validation
Source: https://github.com/damianpapadopoulos/auto-claude-skills/tree/main/skills/runtime-validation
Command: npx skills add https://github.com/damianpapadopoulos/auto-claude-skills --skill runtime-validation-damianpapadopoulos

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

This Skill unit addresses the challenge of verifying that a change in a software application actually functions as intended through real-world interfaces, providing a safety net during the review process and upon explicit validation requests.

Core Features & Use Cases

  • Realistic Context Validation: Validates features in a manner that mirrors real user interactions, including browser E2E, API smoke, CLI checks, and accessibility, performance, and visual-regression audits.
  • Phase-aware PDLC Orchestration: The Skill aligns with the PDLC phases, including DISCOVER, DESIGN, PLAN, IMPLEMENT, REVIEW, SHIP, and LEARN, offering phase-specific skill routing and hints.
  • Safety and Security: Enforces execution of safety-relevant paths, ensuring critical aspects such as authentication, authorization, data deletion, and payments are not overlooked.

Quick Start

To validate a feature, use the runtime-validation skill with the command 'validate the feature' or 'run e2e' during the REVIEW phase.

Frequently Asked Questions about runtime-validation

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

FAQPage Schema
How do I validate software features through realistic user interactions?

Runtime validation verifies software features by executing realistic scenarios across browser, API, and CLI paths. It mirrors real user interactions to ensure functionality and compliance with specified requirements during the review phase.

Can I run accessibility and performance testing without writing custom scripts?

Yes, runtime validation integrates tools like axe-core and Lighthouse to conduct accessibility and performance audits. It orchestrates these checks automatically, validating features without requiring manual script creation for standard compliance checks.

What is the best way to automate end-to-end checks during the software review phase?

The best way to automate end-to-end checks is using phase-aware orchestration aligned with the PDLC. Triggering validation during the REVIEW phase executes browser E2E, API smoke tests, and CLI checks to provide a safety net.

Does runtime validation work with Playwright and curl for API and browser testing?

Yes, runtime validation requires tools like Playwright for browser E2E testing and curl for API and CLI checks. It uses these dependencies to execute realistic scenarios and verify feature functionality across different interfaces.

How do I ensure security and safety paths like authentication are tested during feature validation?

Runtime validation enforces the execution of safety-relevant paths to ensure critical aspects like authentication, authorization, data deletion, and payments are not overlooked during the software review and testing process.

What types of software testing are covered by realistic context validation?

Realistic context validation covers browser E2E, API smoke tests, CLI checks, visual-regression audits, alongside accessibility and performance testing. It validates features comprehensively across multiple interfaces and compliance dimensions.