Explore the guides +
Skills/verify-work
Companion / SKILL GUIDE

verify-work

Check what changed. Show what actually ran.

“Tests pass” is useful only when you know which tests ran and what they cover. This skill traces the change through its consumers and runtime paths, selects relevant checks, and records the results honestly.

When I’d use it

Use it after implementation, after a fix, or before handing work over for review. It verifies a change; it does not fix product code. It may add tests when an acceptance criterion or invariant needs coverage.

Before you start

Give it the change or base commit, the original request, and any checks already run. If the code covered by a passing check hasn’t changed, there’s no reason to rerun it just for ceremony.

Install it. Then give it a task.

Run this in your project’s terminal. Choose your coding agent in the installer, then start a new agent session if it needs one to discover the skill.

TERMINAL
$ npx skills add akdevsaha-dev/factory-skills --skill verify-work

Once installed, send a prompt like the ones below to your agent. These are example requests to adapt to your own project, not terminal commands or recorded results.

If slash commands aren’t available in your agent, write “Use the verify-work skill to…” and describe the same task.

New to skills? Start with the installation walkthrough

What happens next

  1. Maps the diff to affected contracts, data flow, consumers, and runtime.
  2. Chooses checks based on that impact.
  3. Runs narrow checks before broader integration and runtime checks.
  4. Reports results, concrete failures, and checks that couldn’t run.

A few ways to ask

5 examples

Copy the one closest to your task. Replace names, paths, dates, and refs with ones that exist in your project.

01

Verify the current change

SEND TO YOUR AGENT
› /verify-work check the current changes against the original CSV export request. Include filtering, escaping, and the download behavior.

Restating the intent helps distinguish “it builds” from “it does what I asked.”

02

Check a branch

SEND TO YOUR AGENT
› /verify-work verify the change against main. Use the acceptance criteria in the task description and report skipped checks with reasons.

Name a base ref your local repository has.

03

Recheck a fix

SEND TO YOUR AGENT
› /verify-work re-verify the retry fix. The previous failure was a duplicate request after a timeout. Focus on the paths affected by the fix.

Give it the observed failure so it can check the right thing.

04

Verify a backend change

SEND TO YOUR AGENT
› Use verify-work on the order validation change. Check accepted and rejected payloads and the callers of the changed contract.

A backend-only validation change should get relevant tests and API checks; a browser is needed only if an affected page must be exercised.

05

Be explicit about unavailable services

SEND TO YOUR AGENT
› /verify-work verify the email job change using our existing provider fake. Separate local evidence from anything that would require real provider credentials.

A fake can establish local behavior. It does not prove delivery through the real provider.

What to look for in the result

An impact map, commands and results, findings, and a status. Checks blocked by a service or credentials must be marked not run. The skill does not turn an unverified path into a passing claim.

A thing worth watching

Passing types and a build don’t prove runtime behavior. On the other hand, running every unrelated test doesn’t make the evidence stronger. Ask for checks tied to what changed.

Use it with

Based on the repository’s skill instructions.Read the source
PUT IT INTO PRACTICE

Build a workflow you can repeat.

Follow the step-by-step guide to working with agents.

Explore Learn