verification-before-completion
Verify work before claiming completion
Também disponível em: Dimon94,Cycleaddict,Cygnusfear,davila7,CodingCossack,ANcpLua,obra
AI assistants often claim work is complete without running verification commands. This skill enforces evidence-based verification by requiring fresh command output before any success claims, preventing false completion reports.
Baixar o ZIP da skill
Upload no Claude
Vá em Configurações → Capacidades → Skills → Upload skill
Ative e comece a usar
Testar
A utilizar "verification-before-completion". Is the feature complete?
Resultado esperado:
- I cannot claim completion until I verify. Running test suite: npm test
- Test output: 42/42 tests passed, 0 failures, 0 skipped
- Running build: npm run build
- Build output: Build successful, exit code 0
- All verification complete. Feature is ready with test and build evidence.
A utilizar "verification-before-completion". Did the bug fix work?
Resultado esperado:
- Let me reproduce the bug scenario to verify. Running the original failing command
- Bug scenario output: Command completed successfully, no error produced
- The issue is resolved - the original error no longer occurs
A utilizar "verification-before-completion". Can I merge this PR?
Resultado esperado:
- Running full test suite: npm test
- Test output: All 156 tests passing
- Running build: npm run build
- Build output: Success, exit code 0
- Linting: No errors found
- All checks pass. PR is ready for merge.
Auditoria de Segurança
SeguroThis skill contains only markdown documentation with behavioral instructions for AI assistants. The static scanner misinterpreted documentation examples and formatting as executable code. All reported findings are false positives - there is no actual code, no external commands, no network operations, and no cryptographic operations in this skill. The source_url at skill-report.json:6 is legitimate metadata, and backtick-formatted examples in SKILL.md are documentation, not shell execution.
Fatores de risco
🌐 Acesso à rede (1)
📁 Acesso ao sistema de arquivos (1)
Pontuação de qualidade
O Que Você Pode Construir
Pre-commit verification
Run tests, linters, and builds before committing code changes
Bug fix validation
Verify bug fixes by reproducing the original issue and confirming resolution
Sprint completion checks
Validate all acceptance criteria are met with actual test results
Tente Estes Prompts
Are the tests passing? Show me the full test command output with the pass/fail counts.
Run the build command and show me the exit code and any error output.
Reproduce the original bug scenario and confirm the issue is resolved. Show me the command and its output.
Review all PR requirements and verify each one with actual test results or build output.
Melhores Práticas
- Always run the full verification command fresh when claiming success
- Read the complete output including exit codes and failure counts
- Report actual status with evidence rather than assumptions
Evitar
- Claiming tests pass without running the test command
- Saying work looks correct without verification output
- Trusting agent success reports without independent verification