---
name: Verify
slug: verify-5
category: Quality
description: Verify runs the app, relevant command, or focused server flow after a code change and reports concrete evidence of what passed, what was not verified, and remaining risk. Use it when a task is not finished until the change is exercised.
github: "https://github.com/oboard/claude-code-rev/tree/main/src/skills/bundled/verify"
language: TypeScript
stars: 3281
forks: 3821
install: "npx degit https://github.com/oboard/claude-code-rev/tree/main/src/skills/bundled/verify ~/.claude/skills/verify"
installs_to: ~/.claude/skills/verify
source_path: src/skills/bundled/verify/SKILL.md
collection_size: 2
category_size: 1354
collection_url: "https://dirskills.com/collections/oboard/claude-code-rev"
added: 2026-08-17T07:08:32.386Z
last_synced: 2026-08-17T07:08:32.386Z
canonical_url: "https://dirskills.com/skills/verify-5"
---

# Verify

Verify runs the app, relevant command, or focused server flow after a code change and reports concrete evidence of what passed, what was not verified, and remaining risk. Use it when a task is not finished until the change is exercised.

**Install:**

```bash
npx degit https://github.com/oboard/claude-code-rev/tree/main/src/skills/bundled/verify ~/.claude/skills/verify
```

## README

# Verify

Use this skill when a task is not finished until the change is exercised.

## Goal

Produce a short verification result grounded in execution, not inference. Prefer the narrowest check that proves the changed behavior works.

## Workflow

1. Identify the changed surface area.
2. Pick the smallest realistic verification path.
3. Run the relevant command or request flow.
4. Capture the observable result: exit status, key output, HTTP status, or changed behavior.
5. Report what passed, what was not verified, and any remaining risk.

## Rules

- Do not claim success without running something.
- Prefer focused checks over broad smoke tests.
- If the repo has no formal test target, use the nearest runnable workflow.
- If a check is blocked by environment limits, state that explicitly.
- Include exact commands when they are useful to repeat the verification.

## Verification Patterns

### CLI changes

- Run the exact command path affected by the edit.
- Check help text, flags, output formatting, exit codes, and side effects.
- For interactive flows, prefer the most scriptable subcommand first.

See `examples/cli.md`.

### Server changes

- Start only the needed service.
- Exercise the changed route, handler, or background path.
- Validate status code, response shape, logs, and failure handling.

See `examples/server.md`.

## Reporting Format

- `Verified:` what you ran and what passed.
- `Not verified:` anything you could not run.
- `Risk:` the main remaining uncertainty, if any.