change-validation

Validates Cockatails-list changes via targeted tests and smoke checks across UI and data flows.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/DemchaAV/Cockatails-list --skill change-validation
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: change-validation
Source: https://github.com/DemchaAV/Cockatails-list/tree/main/.agent/skills/change-validation
Command: npx skills add https://github.com/DemchaAV/Cockatails-list --skill change-validation

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Validate Cockatails-list changes before finishing a task by ensuring modifications are rigorously tested and validated with smoke checks.

Core Features & Use Cases

  • Create or update tests for changed behavior to maintain coverage.
  • Run targeted validations and smoke checks to prove end-to-end correctness.
  • Generate a clear report detailing passes, blockers, and next steps, including a manifest version bump when needed.

Quick Start

After modifying code or data, run the change-validation workflow to generate tests, execute validations, and compose a final report.

Frequently Asked Questions about change-validation

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

FAQPage Schema
How do I validate code changes with smoke checks after modifying HTML, CSS, or JS files?

To validate code changes, run the change-validation workflow to execute targeted tests and smoke checks across HTML, CSS, JS, and JSON files. This workflow ensures end-to-end correctness by generating tests for modified behavior and reporting blockers.

What is the best way to automate testing for UI and data flow updates?

Automating testing for UI and data updates requires creating or updating tests for changed behavior and running targeted validations. This process proves end-to-end correctness and outputs a report detailing passes, blockers, and next steps.

Do I need to write my own tests before running smoke checks on modified code?

You do not need to write tests manually beforehand; the validation workflow creates or updates tests for changed behavior automatically. It then executes these validations and smoke checks to verify end-to-end correctness across UI and data flows.

How does code change validation handle manifest version bumps?

Code change validation handles manifest version bumps by evaluating validation results and reporting them with next steps. It automatically includes a version bump in the final report when relevant to ensure accurate tracking of validated modifications.

Why does my UI validation report include blockers after running smoke checks?

Your UI validation report includes blockers because the smoke checks identified failures in end-to-end correctness across HTML, CSS, JS, or JSON modifications. The report details these blockers alongside passed checks to guide your next steps.