verification-before-completion
/verification-before-completion
Wymaga uruchomienia polecenia weryfikującego i przeczytania jego wyniku przed deklaracją sukcesu i przed commitem.
Ocena i bezpieczeństwo
- Pliki w paczce
- 2
- Skrypty
- 0
- Komentarze HTML
- 0
- Adresy URL w SKILL.md
- 0
Brak sygnałów. Repozytorium zmienione 05.11.2026, bez odwołań do wycofanych modeli i API.
MIT, otwarta: można używać i zmieniać, z zachowaniem informacji o autorze.
Co robi i kiedy
Wymaga uruchomienia polecenia weryfikującego i przeczytania jego wyniku przed deklaracją sukcesu i przed commitem.
Oryginalny opis (EN)
Use when about to claim work is complete, fixed or passing, and before committing or opening a PR. Requires running the verifying command and reading its output before any success claim.
Jak działa
- The gate
- What each claim requires
- Definition of done
- Red flags
- When it applies
Podgląd SKILL.md
---
name: verification-before-completion
description: Use when about to claim work is complete, fixed or passing, and before committing or opening a PR. Requires running the verifying command and reading its output before any success claim.
---
# Verification Before Completion
Evidence before claims, always.
```
NO COMPLETION CLAIMS WITHOUT FRESH VERIFICATION EVIDENCE
```
If you have not run the verifying command in this message, you cannot claim it passes.
## The gate
Before claiming any status or expressing satisfaction:
1. **Identify** the command that proves the claim.
2. **Run** the full command, fresh.
3. **Read** the full output, check the exit code, count the failures.
4. **Compare** the output to the claim. If it does not confirm it, state the actual status with the evidence.
5. **Only then** make the claim, with the evidence attached.
Skipping a step is not verifying.
## What each claim requires
| Claim | Requires | Not sufficient |
|---|---|---|
| Tests pass | Test command output showing 0 failures | An earlier run, "should pass" |
| Linter clean | Linter output showing 0 errors | A partial check |
| Build succeeds | Build command with exit code 0 | The linter passing |
| Bug fixed | The original symptom now passes | "I changed the code" |
| Regression test works | A red-green cycle: it passes, you revert the fix, it fails, you restore the fix, it passes | It passed once |
| A subagent finished | The diff shows the changes and you checked them | The subagent said "success" |
| Requirements met | A line-by-line check against the spec or plan | The tests passing |
For requirements: re-read the plan or spec, make a checklist, verify each item, then report the gaps or the completion.
## Definition of done
A task is done when its acceptance criteria are met and the standing conditions hold. The acceptance criteria are what the task asked for. The standing conditions are what every task owes:
- The verifying command passes, run fresh, and you read its output.
- No new warning, and no test skipped or removed to get there.
- No debug output, commented-out code or stray file is left behind.
- The documentation and the changelog that the change touches are updated.
- The user's request is answered, not only the code written.
Criteria met without the conditions is not done. Conditions met without the criteria is not done either.
## Red flags
Stop if you are about to use "should", "probably" or "seems to"; express satisfaction ("Great!", "Done!") before verifying; commit, push or open a PR without verifying; trust an agent's success report; rely on a partial check; or feel tired and want it over. Different wording does not exempt you: any phrase that implies success before you ran the check is covered.
## When it applies
Always before any success or completion claim, any positive statement about the state of the work, committing, opening a PR, finishing a task, moving to the next task, and handing work to or accepting work from a subagent.
Pliki w paczce (2)
- SKILL.md 3 KB
- meta.yaml 1 KB
Wersje
| Repozytorium | Wynik | Licencja |
|---|---|---|
| Ta strona · LILLINH/14All | 100 | MIT |
| jjuraszek/pi-gauntlet | 100 | MIT |
| GanyuanRan/Aegis | 100 | MIT |
| mvschwarz/openrig | 100 | Apache-2.0 |
| nikospavlopoulos/devops-mutant-powers | 100 | MIT |
| FrancoStino/opencode-skills-collection | 100 | MIT |
| foryourhealth111-pixel/Vibe-Skills | 100 | Apache-2.0 |
| rootcastleco/rei-skills | 100 | MIT |
| Montinou/triqual | 100 | MIT |
Migawka bazy z 13.11.2026 · wersja paczki ebef69ec458d (skrót SHA-256 całej paczki)
Pobrania w ostatnich 30 dniach: 0 · ranking
Zgłoś problem z tym skillem: szkodliwa treść, błędny opis albo prośba autora o usunięcie.
Podobne skille
- 100verifying-before-completion
Wymaga uruchomienia poleceń weryfikacyjnych i potwierdzenia ich wyniku przed każdym twierdzeniem o sukcesie. - 100verify
Wymaga uruchomienia poleceń i potwierdzenia wyniku przed każdym twierdzeniem o sukcesie, commitem lub PR. - 100verify
Wymaga uruchomienia poleceń weryfikacyjnych i potwierdzenia wyniku przed każdym twierdzeniem o sukcesie.