verify-and-stop

Prove existing work meets acceptance conditions without expanding scope. Use for validation-only tasks, completion checks, focused gate runs, and last-mile proof.

109,139
installs: 0 up / 0 down, score 0.00
votes: 115,798
repo stars
Updated: less than a month ago
In the catalog since: 18 Sept 2026
From: juliusbrussee/caveman

Get it through your agent npx skills add juliusbrussee/caveman@verify-and-stop

Skill instructions

Rendered from the published SKILL.md, 12 lines.

Verify and stop

Translate acceptance conditions into smallest sufficient proof set.

Reuse still-current results with matching repository state.
Run focused checks before wider gates.
Distinguish pass, fail, unavailable, and blocked exactly.
Do not edit product code unless verification request includes fixes.
Do not add polish, cleanup, or unrelated tests after criteria pass.

Stop immediately when acceptance proof is complete. Report commands, results, and unresolved risk only.

Get it through your agent

Call the Graph-of-Skills MCP server's retrieve_skill_bundle tool and it returns this skill's text inside your budget.

{
  "tool": "retrieve_skill_bundle",
  "arguments": {
    "query": "verify-and-stop"
  }
}

New to this? Set up Graph-of-Skills or get a free key. The text on this page comes from its authors: how skills are sourced and what we check. If none fits your task, your agent can write a skill for your own library. To keep a skill from your own library on a machine, see how to install one of your skills.

Share on X Share on LinkedIn Share on Bluesky Share on Hacker News

Share on Reddit

Source

Source repository juliusbrussee/caveman
Listing on skills.sh

From juliusbrussee/caveman via skills.sh

Related skills

verification-before-completion
Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always
257,969 installs
safe-refactor
Restructure code while preserving behavior. Use for extraction, consolidation, ownership moves, or cleanup where verification must bracket structural edits.
110,727 installs
finishing-a-development-branch
Use when implementation is complete, all tests pass, and you need to decide how to integrate the work
218,979 installs
explore-run
Rigor Improve / Rigor Explore run leaf skill for bounded exploratory evidence in deep learning research repositories. Use when the researcher explicitly authorizes exploratory runs such as small-subset validation, short-cycle guess-and-check, batch sweeps, idle-GPU search, or quick transfer-learning trials, with fair-comparison caveats and no-overclaim summaries in `explore_outputs/`. Do not use for end-to-end exploration orchestration on top of `current_research`, trusted baseline execution, conservative training verification, default routing, verified SOTA claims, or implicit experimentation.
340,689 installs
review-loop
Iterative worker-reviewer cycle that spawns a critic subagent to score work 1-10 and provide actionable feedback, then revises until a quality gate is met. Use when implementing features, writing specs, reviewing existing code, or completing any task where quality matters more than speed. Trigger phrases: "use review-loop", "polish this", "iterate on this", "/review-loop", "review with feedback loop".
108,829 installs