Verify that existing work meets its acceptance conditions using the smallest sufficient set of checks. Reuse results that still match the repository state, report outcomes precisely, and stop once the evidence is complete without adding unrelated work.
Prove existing work meets acceptance conditions without expanding scope. Use for validation-only tasks, completion checks, focused gate runs, and last-mile proof.
verify-and-stop checks whether existing work meets its acceptance conditions, using only the checks needed to establish that result. It identifies the minimum evidence required and runs focused checks before broader ones. Earlier results can be reused when they still match the repository’s current state and remain valid. Reports distinguish four outcomes: pass, fail, unavailable, and blocked.
Use it to confirm that implemented work is complete or to verify only the conditions specified in a request. It helps when you want to check results without expanding the scope, or gather the evidence needed to demonstrate completion.
It does not edit product code unless the verification request includes fixes. Once the conditions pass, it adds no polishing, cleanup, or unrelated tests. It stops when sufficient evidence is available and reports only commands, results, and unresolved risks.
This overview was written by AI (OpenAI Codex) from the public SKILL.md. Check the original below for the exact behavior.
AI rated this skill on four points using only the contents of its SKILL.md. Stars and popularity are not taken into account.
The total counts each point as A = 25, B = 15, C = 5. Rated by AI (OpenAI Codex) as of Oct 20, 2026. Treat it as a guide and read the original before installing.
Review the instructions the agent will receive before you install.
Translate acceptance conditions into smallest sufficient proof set.
Stop immediately when acceptance proof is complete. Report commands, results, and unresolved risk only.
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Delegate code lookup, small edits, and diff reviews to three specialized subagents. Their compact, structured results help conserve the main agent's context, with guidance on when to delegate and when to keep work in the main conversation.
Make agent replies shorter and easier to scan by putting answers first and removing filler. Preserves technical details, exact commands, numbers, and essential conditions while keeping the user's chosen language.
Create short commit messages using Conventional Commits, a format that labels the type of change. Emphasize intent, keep the subject concise, and include explanatory text when breaking changes, security fixes, data migrations, or reversions require context.
Compress memory files and task lists into shorter wording to reduce input tokens. Keeps code and document structure intact, saves a readable backup separately, and sends the text to the configured model provider.
Find LLM workflows in a codebase and label them by the job they perform, so Caveman Cloud can separate spending by workflow. Present a labeling proposal for approval, apply focused code changes, and check an affected execution path.
Review Caveman Cloud spending, latency, errors, and potential improvements using current reports and traces, or individual execution records. Produce findings tied to time windows and trace IDs, while keeping measured costs, estimated opportunities, and verified savings separate.