Individual skill

verification-before-completion

0upvotes

Use when preparing to say a change is complete, a defect is fixed, checks pass, or a commit or release is ready.

plugins/agent-foundry/skills/verification-before-completion/SKILL.md

Read pinned source

Source commit e1a5a792f45899379b42c06e7a332ff40caa7c2f

What was checked

Matches the observed repository HEAD: Yes
Scanner rules are current: No
Repository scan complete: No
Skill scan complete: Yes
Observed behavior: Not checked yet
Last checked: Nov 5, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings): 13
Repository last updated: Oct 22, 2026
License: MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

agent-skills Repository topic
ai-agents Repository topic
claude-code Repository topic
claude-code-plugin Repository topic
codex Repository topic
developer-tools Repository topic
firebase Repository topic
game-development Repository topic
prompt-engineering Repository topic
unity Repository topic
engineering Derived category

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files

SKILL.mdcore · 2,168 bytes

Read excerpt


# Verification Before Completion

Match each completion claim to fresh evidence from the current revision. This
skill checks the claim; it does not replace a task contract, QA plan, or the
project's test procedure.

## Check the claim

1. Write down the exact behavior or state you intend to report.
2. Select the smallest relevant verification channel: automated test, build,
   manual reproduction, artifact inspection, or explicit user acceptance.
3. Run or inspect that channel after the last relevant edit. Record the command
   or manual steps, target revision, result, and any skipped scope.
4. Compare the result with the claim. A passing linter does not prove a build;