agentleFS
Sign inStart free
aprameyakaprameyak/coding-skills/verify-work/SKILL.md

verify-work

Skill1 starsChanged 41 days agoMITView on GitHub

Verify changes before claiming done. Use when finishing implementations, fixes, or refactors, or when the user asks if work is complete.

8 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

3 rules. 0 are common, 3 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 8 edited versions we read keep these.

  • 3

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Run the project’s relevant checks (tests, typecheck, lint, build).

    line 11
  2. Distinctive:

    Never mark complete on untested critical paths.

    line 29
  3. Distinctive:

    If checks cannot run, say why and what was verified instead.

    line 30

“Common” is measured: kept by at least 6 in 10 of the 8 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Verify Work

Before Claiming Done

  1. Re-read the original request; confirm every requirement is met.
  2. Run the project’s relevant checks (tests, typecheck, lint, build).
  3. Exercise the changed path manually when feasible.
  4. Inspect the diff for accidental scope.
  5. Confirm no secrets, debug leftovers, or broken imports.

Evidence

Report what was run and the outcome:

Checks:
- <command> → pass|fail (summary)
Behavior checked: ...
Remaining risks: ...

Rules

  • Never mark complete on untested critical paths.
  • If checks cannot run, say why and what was verified instead.
  • Fix failures before expanding scope.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free