dev-validate

Execute automated unit, integration, and browser end-to-end tests against user stories.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/MaxGiu67/plugin-MUCC --skill dev-validate
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: dev-validate
Source: https://github.com/MaxGiu67/plugin-MUCC/tree/main/dev-methodology/skills/dev-validate
Command: npx skills add https://github.com/MaxGiu67/plugin-MUCC --skill dev-validate

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Ensures implemented user stories meet acceptance criteria by automating unit, integration, and browser end-to-end validation, and by combining quality and security pre-checks so releases are safe and verifiable.

Core Features & Use Cases

  • Quality & Security Pre-checks: Runs quality and security analysis and records Quality Score and Security Score in the validation report to enforce gates before production.
  • Automated Test Execution: Executes unit and integration test suites, collects coverage metrics, and maps failing tests to user stories for targeted fixes.
  • Interactive E2E Browser Validation: When browser automation tools are available, exercises critical-path flows in a browser, captures screenshots, console logs, and network evidence for failed flows.
  • Reporting & Decisioning: Produces a structured validation report and sprint review artifacts, updates test maps and status files, and supports an iterative fix-and-retest cycle until approval criteria are met.

Quick Start

Run the dev-validate workflow to execute automated tests, perform E2E browser checks if available, and generate the specs/08-validation.md validation report.

Frequently Asked Questions about dev-validate

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

FAQPage Schema
How do I automate end-to-end validation and QA reporting for implemented user stories?▼

End-to-end validation executes automated unit, integration, and browser tests against user stories to verify pass/fail status, coverage, and critical-path behavior. It generates validation reports containing test counts, coverage metrics, screenshots, and console logs.

What is included in a sprint validation test report for release readiness?▼

A sprint validation report includes test counts, pass/fail lists, coverage percentages, quality and security scores, E2E screenshots, console logs, and network evidence. It maps failing tests to user stories and updates validation artifacts in specs.

How do I run automated browser E2E tests and capture screenshots for failed critical-path flows?▼

Browser end-to-end tests execute critical-path flows and capture screenshots, console logs, and network evidence for failed paths when browser automation tools are available. This interactive validation supplies verifiable evidence for sprint reviews.

Does automated test execution map failing unit and integration tests to user stories for targeted fixes?▼

Automated test execution runs unit and integration suites, collects coverage metrics, and maps failing tests directly to user stories. This enables targeted fixes and supports an iterative fix-and-retest cycle until approval criteria are met.

Can I enforce quality and security gates before production using automated validation checks?▼

Automated validation runs quality and security pre-checks before production, recording Quality Score and Security Score in the validation report. These pre-checks enforce release gates ensuring deployed user stories are safe and verifiable.

What are the limitations of browser end-to-end validation when automation tools are unavailable?▼

Browser end-to-end validation is limited when browser automation tools are unavailable, restricting the ability to exercise critical-path flows interactively. The workflow still executes unit and integration tests and generates quality and security scores.