Skip to content
Skills Library
Programming · Testing

verification

/verification

Prove that a change works. Use after implementing or fixing anything, before claiming tests pass, and whenever a UI must be checked in a real browser. Covers test selection, running the suite, browser checks across viewports, accessibility basics, and the rule that unexecuted checks are reported as unverified.

Licence
MIT
Last repository change
28.10.2026

Assessment and security

90/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content25 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
2
Scripts
1
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 28.10.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What to check before installing
  • 1 scripts in this package. Review them before installing, as Claude may execute them.

Scripts: scripts/ui_probe.py

What it does and when to use it

Prove that a change works. Use after implementing or fixing anything, before claiming tests pass, and whenever a UI must be checked in a real browser. Covers test selection, running the suite, browser checks across viewports, accessibility basics, and the rule that unexecuted checks are reported as unverified.

Original author description

Prove that a change works. Use after implementing or fixing anything, before claiming tests pass, and whenever a UI must be checked in a real browser. Covers test selection, running the suite, browser checks across viewports, accessibility basics, and the rule that unexecuted checks are reported as unverified.

How it works

  1. Rules
  2. What to test
  3. Browser checks
Original SKILL.md headings · 39 lines, 339 words
SKILL.md preview
---
name: verification
description: Prove that a change works. Use after implementing or fixing anything, before claiming tests pass, and whenever a UI must be checked in a real browser. Covers test selection, running the suite, browser checks across viewports, accessibility basics, and the rule that unexecuted checks are reported as unverified.
---

# Verification

## Rules

- Run it, then report it. Paste the command and the summary line of the output.
- A check you did not run is "not run". A check that could not run is "blocked" with the reason.
- Tests must fail before the fix when you are fixing a bug. Show the red run. For a fix found during your own work, revert it once and confirm a test goes red.
- Run browser interaction suites at least three times. One green run does not rule out a race.
- Isolate test state. Reset the data, clear request interception, and use test data no other step creates. A leaked route or a stray record turns one failure into many.

## What to test

Write tests from acceptance criteria, not from implementation details.

1. Happy path for each criterion.
2. Invalid input at the boundary: empty, too long, wrong type, missing field.
3. Missing resource and server failure.
4. The UI states: pending, error, success, empty.

Prefer a few tests that exercise real behaviour over many that assert on mocks.

## Browser checks

When a browser automation tool is available, run `scripts/ui_probe.py <url> --out <dir>`. It loads the page at 360, 768, and 1280 px, saves screenshots, and reports:

- console errors and failed requests (pass `--ignore-host` for hosts the sandbox blocks; they are listed, not counted)
- horizontal overflow
- inputs without labels, buttons without accessible names, images without alt
- duplicate control names and ARIA references to missing ids
- controls with no visible focus change when reached by Tab (checked at the widest viewport, after transitions settle)
- viewport meta that blocks zoom

The probe does not see wrapped rows, misaligned controls, or text that changes size between states. Only the screenshots show those.

Then exercise the feature with a scripted interaction (click, type, keyboard). Look at the screenshots. A screenshot you did not open is not visual verification.

If no browser is available, say so and list what a human must check.
Files in this package (2)
  • SKILL.md 2 KB
  • scripts/ui_probe.py 8 KB

Versions

RepositoryScoreLicence
This page · AHMADYAZIDALFARISI/Vibe-Coding-Ayasi90MIT
aws-solutions/konductor100Apache-2.0
YuDefine/nuxt-supabase-starter100MIT
assafkip/huntkit100MIT
vercel/vercel-plugin100Apache-2.0
romiluz13/cc10x100MIT
CooCoode/pi-skills100MIT
Aurite-ai/agent-verifier100MIT
fusengine/agents100MIT

Database snapshot: 13.11.2026 · package version 1c201b187e14 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100verify-before-done
    Proves a code change works before calling it done by finding and running the project's build, typecheck, lint and tests, reading the output and fixing failures, plus a browser check for UI changes. Use when finishing any coding task, before saying a change is complete, fixed or…
  • 90unity-verification
    Unity verification rules. Use when checking that a Unity change compiles or works, running Unity tests, building a player, running C# in the Editor, classifying Unity involvement for issue triage or selection, or when Unity cannot run here or the editor is locked.
  • 100runtime-verification
    Verifies implementation works at runtime by discovering and executing dev server startup, API smoke tests, E2E tests, and browser checks. Use after quality checks pass (lint, test, typecheck) to confirm the code actually runs. Use when validating acceptance criteria, running…
  • 90truly-done
    Proves a change works in the running web app. Drives the user's own app in headless Chrome with real clicks and typing, checks each claim against the live page (text, counts, values, URL, console errors, network calls), and answers pass, fail or cannot tell with evidence and a…
  • 90ui-test
    This skill should be used after any UI change and before a commit that touches pages, components or dialogs, and when the user asks to 'test the UI', 'validate the UX', 'check the DX', 'run a UX pass', 'test it in the browser', 'playwright check', or 'run user personas'. Drives…
  • 90browser-qa
    Verifies frontend changes in a real browser or automation with route smoke, critical interactions, two or more viewports, console and network checks, and dev-server lifecycle. Use when a user-facing UI change needs proof that it works. Not for critiquing supplied screenshots (screenshot-review).

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.