Skip to content
Back to skills

Verification Before Completion

ASecurity

Use when claiming a task is complete, before commits, or before PR creation.

  • 8 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added May 28, 2026
ai-agentsgonode

Security analysis

A100/100

Scanned May 28, 2026

npx -y skills add seokan-jeong/team-shinchan --skill verification-before-completion --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Verification Before Completion?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Verification Before Completion
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/seokan-jeong-verification-before-completion/badge)](https://www.skillsdirectory.com/skills/seokan-jeong-verification-before-completion)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: team-shinchan:verification-before-completion
description: Use when claiming a task is complete, before commits, or before PR creation.
user-invocable: false
---

# Verification-Before-Completion Gate

Never claim a task is complete without running a verification command and reading its output. "I believe it works" is not evidence.

## Verification Checkpoints

You MUST verify at each of these triggers:

1. **Before commits** -- run tests/linter, confirm pass
2. **Before PR creation** -- run full validation suite, confirm zero errors
3. **Before task completion** -- run the specific success criteria commands from the task plan
4. **Before moving to next task** -- confirm current task's tests still pass after any late edits

## Required Evidence

Every completion claim must include:

- **Command**: The exact command you ran (copy-paste, not paraphrased)
- **Output**: The actual output (or relevant excerpt for long output)
- **Verdict**: PASS or FAIL based on the output

If you cannot provide all three, you have NOT verified. Go back and run the command.

## Red Flags List

If your completion report contains ANY of these phrases, you have NOT verified -- STOP and actually run a command:

| Red Flag Phrase | What To Do Instead |
|-----------------|--------------------|
| "should work" | Run the test and show it passes |
| "probably fine" | Run the linter/build and show zero errors |
| "seems to" | Read the actual output and report what it says |
| "looks correct" | Run a validator or test that proves correctness |
| "I believe" | Replace belief with evidence -- run a command |
| "likely" | Remove doubt -- execute and observe |
| "I think" | Verify instead of thinking |
| "no issues expected" | Prove it -- run the check |

## Verification Template

Use this format in your completion report:

```
### Verification
- **Command**: `node tests/validate/index.js`
- **Expected**: All validators pass, 0 errors
- **Actual**: 23 validators passed, 0 errors, 0 warnings
- **Verdict**: PASS
```

If the verdict is FAIL, fix the issue before claiming completion. Do not report a task as done with a FAIL verdict.

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.