agentleFS
Sign inStart free
clearsmogclearsmog/claude-skills/verify/SKILL.md

verify

Skill2 starsChanged 9 months agoMITView on GitHub

Verify that changed work actually runs and renders before a commit or before calling a task done. Compiles .typ/.qmd/.py/.R, runs the project's tests and build, and click-tests frontend changes in Chrome. Use before committing, when asked to verify or check work, or when finishing any change to compilable or visual files.

188 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use instinct-export, instinct-import and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • TheKREATORSSkill

    instinct-export

    Export instincts from project/global scope to a file

    Also in 3 projects that use this

  • TheKREATORSSkill

    instinct-import

    Import instincts from file or URL into project/global scope

    Also in 3 projects that use this

  • AviadPSkill

    risk-assess

    Assess the risk and blast radius of a proposed code change before implementing it. Evaluates CI impact, framework-wide vs localized scope, rollback path, and identifies blindspots. Use when user says "what's the risk", "is this safe", "assess the impact", "risk assess", "blast radius", or before applying framework-wide or CI-affecting changes. Do NOT use for code quality review (use code-quality) or plan validation (use design-validator).

    Also in 3 projects that use this

  • diego-tobalinaSkill

    build-fix

    Fix build and compilation errors systematically. Run when build fails.

    Also in 6 projects that use this

  • AaravChadhaSkill

    secure

    Security review with a confidence gate - a finding exists only with a concrete exploit scenario and a high/medium/low confidence rating; everything else goes to a worth-hardening list, never inflated. Sweeps five surfaces: auth gates, secrets hygiene, injection and unsafe sinks, unsafe deserialization/crypto/transport, and LLM tool-use trust boundaries. Reports only, never fixes. Use when the user asks for a security review or to check vulnerabilities, secrets, or auth.

    Also in 3 projects that use this

  • ArvorCoSkill

    specify

    Create feature specification from natural language description. Use when starting a new feature or creating a spec. Triggers on: create spec, specify feature, new feature spec.

    Also in 10 projects that use this

  • +1 more from TheKREATORS

The file

We split this skill into the rules it gives an agent

1 rule. 0 are common, 0 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 167 edited versions we read keep these.

  • 0

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Use the project's own commands when it defines them (package.json scripts, Makefile, justfile, pyproject.toml), in preference to the …

    line 27

“Common” is measured: kept by at least 6 in 10 of the 167 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

Prove the change works. A passing type-check is not proof.

1. Find what changed

In a git repo: git diff --name-only HEAD plus git diff --name-only --cached, plus untracked files from git status --porcelain. Outside git, verify the files touched in this session.

2. Check each file type

ChangedCheck
.typtypst compile the entry file; read the PDF page(s) touched, look for overflow and broken layout
.qmdquarto render the file
.pyuv run python -I -m py_compile <file>; run uv run pytest if the project has tests; run the script itself if it is an entry point and safe to run
.RRscript <file> when it is a standalone script
.html, .tsx, .jsx, .css, .vuebun run build and bun run test if defined (biome check when biome.json exists); then open the page with Claude in Chrome (load the claude-in-chrome skill) and click through the changed flow, checking the console for errors
.md with images or diagramsrender it in the target viewer and confirm the images load
.xlsxrecalculate and scan for #REF!, #DIV/0!, #VALUE!

Use the project's own commands when it defines them (package.json scripts, Makefile, justfile, pyproject.toml), in preference to the defaults above.

3. Report

One line per check: what ran and whether it passed. On a failure, show the relevant output and do not commit. Fix it, or stop and say what is broken. Never report a check as passed when it was skipped; say it was skipped and why.

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