code-change-verification

Use after code, test, packaging, CI, or browser-app changes to choose and run proportionate verification commands and report evidence.

SKILL.md.agents/skills/code-change-verification/SKILL.md

Start from the command documented in AGENTS.md, Makefile, CI, or README.
Run the narrowest meaningful check first, then the repo-level verification target when the blast radius is broad.
For Python package changes, run unit tests and Ruff checks.
For browser or staging changes, run the staging command and E2E or smoke tests.
Report exact commands, pass/fail outcome, skipped tests, warnings, and any files generated by verification.
Do not claim a command passed unless it actually ran.

Generate Vitest + React Testing Library tests for Dify frontend components, hooks, and utilities. Triggers on testing, s...

Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an exist...

Automates browser interactions for web testing, form filling, screenshots, and data extraction. Use when the user needs...