skills.rest
gmolike
gmolikeCOMMUNITY
Explore all skills by this author →
GitHub

verify

Runs the changed code path end-to-end and records evidence numbers before every commit.

Updated Mar 4, 2026
Search Tags:#code quality#debugging#verification#evidence#pre-commit#end-to-end testing#round-trip
One-click install
npx skills add https://github.com/gmolike/Claude-Template --skill verify-gmolike
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: verify
Source: https://github.com/gmolike/Claude-Template/tree/main/.claude/skills/verify
Command: npx skills add https://github.com/gmolike/Claude-Template --skill verify-gmolike

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Green tests alone do not prove that the code you just changed actually works at runtime. This Skill closes that gap by forcing a real execution of the changed flow — starting the app, triggering the exact modified path, and capturing a concrete evidence number (HTTP status, row counts, test counts) instead of vague claims like "works" or "verified". ## Core Features & Use Cases - Context-driven execution: Reads package.json scripts, README, and project standards first so start commands are never guessed, then launches the app or service and waits for readiness. - Hard separation of verification surfaces: Visual/UI verification may be deferred only with a named owner and date, while the data round-trip (build → serialize → validate → read) is never deferrable for contract or schema changes. - RED-verified regression checks: Round-trip tests must fail against the old broken implementation before they count as proof, preventing false confidence. - Use Case: Before committing a fix to a profile-save API route, run the changed flow, observe POST /api/profiles → 201, 3 rows in profiles (vorher 0), reproduce the error path, and record the evidence in the structured report template. ## Quick Start Ask the agent to verify the flow you just changed by running it end-to-end and reporting the evidence numbers before committing.

Frequently Asked Questions about verify

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

FAQPage Schema
How do I verify a code change actually works before committing?▼

Run the changed flow end-to-end: read the project's start commands from package.json, launch the app, trigger the exact modified entry point, and record an evidence number such as an HTTP status, row count, or test count. Green tests alone do not count as verification.

What is the difference between running tests and verifying a flow?▼

Tests check what someone wrote down; verification checks what the software actually does at runtime. Both are required and neither replaces the other — a change is only verified when its real execution produces an observable effect like a response body or database row.

Can visual UI verification be deferred to manual QA?▼

Yes, but only with an explicit note naming who will run it and when. A bare "browser-verify deferred" counts as not verified. The data round-trip for contract or schema changes can never be deferred.

Why does TanStack Query hang in headless browser verification?▼

In automated or headless browsers, navigator reports offline, leaving queries stuck in fetchStatus 'paused'. Set networkMode: 'always' so queries execute, otherwise you end up verifying a loading spinner instead of the real flow.

When is verification not required for a commit?▼

Verification is not needed for diffs with no runtime surface, such as tests-only changes or documentation and markdown edits. Any diff touching production code requires an end-to-end run with evidence before commit.

Related Skills

Explore More Software Engineering Skills→
leonardoacostaleonardoacosta

env-and-secrets

Enforces dotenvx and @t3-oss/env rules for T3 environment variables and secret-safe code.

Community
Intermediate
compozycompozy
2.7k

cy-final-verify

Enforces fresh verification evidence before completion claims, commits, and PR creation.

Official
Advanced
PionpillPionpill
12

develop-test

Generate adversarial IR inputs to test retikz JSON and zod contracts.

Community
Advanced
FFOO6866FFOO6866

Test-Skip Discipline

Detect runtime-result test skips that mask broken system behavior.

Community
Intermediate