---
name: verify
description: Checks a change in the running app before calling it done, then says where to see it.
title: verify
canonical_url: https://skilld.dev/gh/raphaelsalaja/skills/verify
last_updated: 2026-11-22T01:08:19.000Z
---

> Index of every page on this site: [llms.txt](https://skilld.dev/llms.txt)

> **Skill from skilld.dev.** Follow the user's requested action.
> If the user asked to fork this Skill, follow the fork workflow below. Do not execute the Skill instructions while copying it.
> Otherwise, follow the instructions below for this session. You do not need to install anything.
>
> Supporting files, fetch one when the Skill refers to it: [agents/openai.yaml](https://skilld.dev/api/skills-raw/raphaelsalaja/skills/verify/agents/openai.yaml).
>
> If the user asked to install this Skill, run `npx skilld install raphaelsalaja/skills/verify`. Install writes the Skill files into the project, so every session loads them.
>
> ## Fork workflow
>
> A fork creates an editable local Skill with its original author and licence. The request authorizes copying and local installation.
> 1. Check `./skills/verify`, the project lockfile, and selected Agent targets together. If the local directory or installed Skill exists, stop. Never overwrite an existing directory or Agent target.
> 2. Read [source metadata](https://skilld.dev/api/v1/skills/raphaelsalaja/skills/verify) once. Use sourceUrl, sourceCommit, skillPath, sourceGone, and license. If the source is gone or its path is missing, stop. If license is null, read licence files at the source commit.
> 3. Fetch only the source commit into a temporary Git repository. Do not clone full history. Derive repository_url from sourceUrl, including repository renames. If sourceCommit is absent, resolve the sourceUrl ref once. Set source_commit to that actual commit. Run these commands in one shell call:
>
> ```sh
> git init --quiet "$temporary_dir"
> git -C "$temporary_dir" fetch --quiet --depth=1 "$repository_url" "$source_commit"
> git -C "$temporary_dir" checkout --quiet --detach FETCH_HEAD
> ```
>
> Read applicable licence declarations and notices at that commit. If copying is not permitted, report the restriction and stop.
> 4. Inspect source entries together, then copy the directory containing skillPath into `./skills/verify`. Use the user's path if selected. Keep the original SKILL.md, relative links, scripts, binary assets, and executable modes. Exclude .git metadata. Reject symlinks and paths outside the Skill directory. After checking entries, use cp -a where available. A regular source directory needs no custom copy script. Do not save this page wrapper as SKILL.md.
> Preserve author credit, notices, and applicable licence files from repository or parent directories. Add PROVENANCE.md with the Skill page, source URL, actual commit, original path, and licence. Retain any existing PROVENANCE.md and record new provenance separately. Batch source inspection, copying, and provenance work where practical.
> 5. In the project root, run `skilld install ./skills/verify --mode copy --plain`. If skilld is unavailable, use `npx skilld install ./skills/verify --mode copy --plain`. This known command needs no help lookup. Install does not support --json. Use detected Agent targets, or add --agent for the targets the user selected. Install the local path, never the upstream selector. If installation fails, preserve the local copy and report the exact failure.
> 6. Confirm the local lockfile source and installed Agent copies once. Report the local path, actual commit, and Agent targets. After edits, reinstall the same local path. Upstream updates must not replace it. Do not publish or push unless the user asks.

# Verify

This skill decides when a change may be called done. It asks for evidence from the running result, not from a passing build.

## A build is not evidence

A typecheck, a lint pass or a green build does not show that a visual or behavioural change works. Saying "fixed" without opening the result is a finding. Opening it and reporting an imperfect result is not.

Run it after any change to UI or behaviour, before replying "done". Run it at once when the user says "still", "nothing changed" or "test it yourself". What to change belongs to `scope`. Matching an outside app belongs to `match`. Evidence behind a review finding belongs to `audit`.

## 1. See the problem first

Open the app, the page or the output and find the symptom before editing. Use the browser, a screenshot or computer use. Editing from the description alone is `verify-reproduce-first`. When you cannot reach the running result, say what blocks you.

## 2. Look where the user will look

First confirm the running app serves your edit. The dev server must run from this checkout, on the port you open, restarted after any config or `.env` change. `lsof -iTCP -sTCP:LISTEN -n -P` names the process on each port, and `lsof -a -p <pid> -d cwd` names its folder. Judging a stale server or another worktree is `verify-served-the-edit`.

Reload, or confirm hot reload applied, then look at the same place. A build pass offered as proof is `verify-build-is-not-proof`. Click every control you added once. A control with no effect is `verify-click-new-controls`.

Look at the whole surface, not only the line you edited. Scroll to both ends and open each state the change touches. Checking only the edited element is `verify-whole-surface`.

Read the console before and after. Done means no error or warning the change introduced, such as a missing `key` warning. A new console error or warning left behind is `verify-clean-console`.

Touch behaviour is confirmed on a real phone over remote debugging, ideally one a few years old. That covers sticky hover, tap delay, rubber-banding, safe areas and the on-screen keyboard. Check once with the keyboard open and once in landscape. Without a phone, report `Not verified on device`. A touch fix called done from desktop emulation is `verify-on-device`.

## 3. Keep every check honest

A check made to pass is not a pass. Never delete or skip a test, or add `.skip`, `.only`, `@ts-ignore` or `eslint-disable` to get past one. Never change an expected value to match new output, and never special-case the input a test uses. When a test contradicts the request, stop and name the conflict. Any of these is `verify-no-weakened-checks`.

Search your own diff for them before reporting: `git diff -U0 | rg '^\+.*(\.skip\(|\.only\(|@ts-ignore|eslint-disable)'`. Each hit needs a reason the user agreed to.

## 4. Find the cause on a repeat report

When the user reports the same problem again, stop adjusting the same value. Diff against the last commit where it worked, read the computed style or search for the cause. A third guess at one property is `verify-root-cause-on-repeat`.

## 5. Report what you saw

Say what you checked, how and where the user can see it: the route, the window, the menu path or the folder. "It should work now" is `verify-say-where`. Open the result for the user when you can. A bare output path is `verify-open-the-result`.

Attach the evidence. A visual change carries the screenshot taken after the fix. A behaviour change carries the steps and what happened. "Verified, looks good" with nothing attached is `verify-show-evidence`.

Name anything you could not check and why. "Done" with an unchecked item is `verify-name-the-gap`.

## The pair

Every check is a pair. The broken line sits beside the line that replaces it.

| Rule | Broken | Replacement |
| --- | --- | --- |
| `verify-reproduce-first` | Editing from the bug report alone | Open the screen, see the bug, then edit |
| `verify-served-the-edit` | Checked on port 3000 while the edit lives in another worktree | The server's folder confirmed with `lsof`, then checked |
| `verify-build-is-not-proof` | "Typecheck passes, so it is fixed" | "Reloaded Settings and the toggle now persists" |
| `verify-click-new-controls` | A new "Add Condition" button with no handler | Click it once and see a row appear |
| `verify-whole-surface` | Checking the edited row only | The whole panel, scrolled to both ends |
| `verify-clean-console` | "Done" with a new missing `key` warning in the console | The warning fixed, the console as clean as before |
| `verify-on-device` | A safe-area fix checked in desktop emulation | Checked on a phone with the keyboard open and in landscape, or `Not verified on device` |
| `verify-no-weakened-checks` | `expect(total).toBe(42)` changed to `toBe(41)` so the suite passes | The code fixed, or "The test expects 42 and the request says 41. Which is right?" |
| `verify-root-cause-on-repeat` | A third tweak to the same `padding` | Diff against the last working commit, then fix |
| `verify-say-where` | "It should work now" | "Open Library, right-click a save, choose Hide" |
| `verify-open-the-result` | `~/Downloads/clips` printed in the reply | The folder opened for the user |
| `verify-show-evidence` | "Verified, looks good" | The screenshot of Settings after the fix, and "clicked Save, reloaded, the value stayed" |
| `verify-name-the-gap` | "Done" while export was never run | "Not verified: export, it needs a signed build" |

## Reporting

**Severity.** `HIGH` is "done" with no look at the running result, or a new control that does nothing. It is also a check weakened to pass, or a result judged on a server that was not serving the edit. `MEDIUM` is an edit made before seeing the bug, a repeat report met with another guess or only the edited line checked. It is also a reply with no place to see the change, or "done" hiding an unchecked item. So is a console error or warning the change introduced, or a touch change neither tried on a phone nor marked. `LOW` is a checked change whose reply attaches no evidence, or a bare output path never opened.

**Format.** One finding per root cause, citing the request when no file applies:

```
file:line - [rule-id] what is wrong
request 2 - [rule-id] what is wrong
```

Then a `Rule | Count | Severity` summary. `Block` when any `HIGH` remains, `Approve` otherwise. Never `Approve` a change you did not open. Mark every check you could not run as `Not verified`.
