Skip to content
Skills Library
Programming · Testing

testing-verification

/testing-verification

Design or assess tests, acceptance checks, CI coverage, and browser verification. Use when verification is the main deliverable or requires specialist judgment; ordinary implementation can keep its focused checks inline.

Licence
Apache-2.0
Last repository change
01.10.2026

Assessment and security

95/ 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.
Content30 / 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
4
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

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

Licence

Apache-2.0, otwarta: można używać i zmieniać, z zachowaniem licencji i informacji o zmianach.

What it does and when to use it

Design or assess tests, acceptance checks, CI coverage, and browser verification. Use when verification is the main deliverable or requires specialist judgment; ordinary implementation can keep its focused checks inline.

Original author description

Design or assess tests, acceptance checks, CI coverage, and browser verification. Use when verification is the main deliverable or requires specialist judgment; ordinary implementation can keep its focused checks inline.

How it works

  1. Delegation
  2. Select evidence
  3. Browser work
  4. Run and finish
Original SKILL.md headings · 29 lines, 316 words
SKILL.md preview
---
name: testing-verification
description: Design or assess tests, acceptance checks, CI coverage, and browser verification. Use when verification is the main deliverable or requires specialist judgment; ordinary implementation can keep its focused checks inline.
---

# Testing Verification

Verify observable behavior at the narrowest reliable level, using project conventions and the failure cost to choose coverage.

## Delegation

Run in the main conversation by default. Delegation can increase usage: obtain explicit approval for the proposed agent count and scope before using subagents. Reuse that approval within its bounds; ask again before expanding the approved count or scope.

## Select evidence

Inspect relevant contracts, nearby tests, fixtures, commands, and CI definitions. Choose checks that can fail for the behavior in question, including important negative paths. Use [test-strategy.md](references/test-strategy.md) when the test level or coverage tradeoff is unclear.

Prefer existing test infrastructure and stable fixtures. Test public behavior rather than incidental implementation details; avoid hidden network dependencies, production data, and timing-based assertions. Add automation when it protects meaningful behavior, without writing tests that simply mirror trivial edits.

## Browser work

Use the browser surface the host and project policy designate for interactive, exploratory, screenshot, and visual comparison work. If that surface fails, troubleshoot it before falling back to another, and say which surface produced the evidence. When the user named a specific surface, get their direction before substituting a different one.

Source-controlled Playwright E2E provides repeatable regression coverage. Keep it distinct from a manual Browser pass. Read [ui-visual-verification.md](references/ui-visual-verification.md) when comparison conditions or visual ambiguity matter.

## Run and finish

Run focused checks and required repository gates. Investigate failures before broadening, and rerun only affected checks after a fix. Reuse passing results for unchanged responsibilities and equivalent conditions. A commit, PR, merge, or handoff alone does not justify repeating a suite.

Follow explicit testing budgets. Propose a broader suite only when it could resolve a material gap; ask when project policy or unapproved cost requires it. Finish once the evidence is sufficient.

Report commands, results, relevant coverage, any browser surface used, and remaining gaps. Do not claim behavioral or visual verification from static checks alone.
Files in this package (4)
  • SKILL.md 3 KB
  • agents/openai.yaml 1 KB
  • references/test-strategy.md 3 KB
  • references/ui-visual-verification.md 1 KB

Versions

The database has no other skills named testing-verification.

Identical content appears in 1 other GitHub folders. We show one copy with the highest score.

Database snapshot: 13.11.2026 · package version 7097d898ee7a (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

  • 100test-gen
    Use this skill after code changes to generate or update targeted tests, acceptance coverage, and regression checks with stack-aware verification.
  • 90testing-python
    Stratégie de Tests Python 3.14+. Use when writing tests, reviewing test coverage, or setting up testing.
  • 90qa-engineer
    Use when designing test suites, writing acceptance tests, validating an implementation against a spec, or planning test coverage before implementation. Trigger: /qa-engineer.
  • 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…
  • 100typescript-testing
    TypeScript testing patterns with Jest/Vitest including unit tests, integration tests, mocking strategies, and coverage. Use when writing TypeScript tests.
  • 90verification
    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…

Feedback and reports

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