Results for “result-verification”
29 skillsMore results
Verify
Verify code changes work by running them. Proves through execution, not just inspection.
3
Verify
Combined verification — recite (description quality via cold-read prediction) + validate (schema compliance) + review (health checks). Use as a quality gate after creating notes or as periodic maintenance. Triggers on "/verify", "/verify [note]", "verify note quality", "check note health".
3 · bundle
Verification
Verification-before-completion discipline ensuring all success criteria are met, tests pass, and reviews complete before declaring work done.
1.7k · bundle
Speckit Verify Tasks
Verify tasks marked [X] in tasks.md are implemented, not phantom completions (marked done but backed by missing or dead code).
11
Verify
Verify that a change really works before you claim completion
1
Verification Before Completion
Enforces running verification commands and confirming output before claiming work is complete, fixed, or passing, to prevent false success claims.
247k
Openspec Verify Change
Verify implementation matches change artifacts. Use when the user wants to validate that implementation is complete, correct, and coherent before archiving.
0
Verification Before Completion
Enforces running verification commands and confirming output before claiming work is complete, fixed, or passing, ensuring evidence precedes any success claims.
0
Verification Gate
Enforces a verification gate before any completion claim, requiring fresh command output as evidence.
1 · bundle
Speckit Verify Tasks Run
Verify tasks marked [X] in tasks.md are implemented, not phantom completions (marked done but backed by missing or dead code).
11
Openspec Verify Change
Verify implementation matches change artifacts. Use when the user wants to validate that implementation is complete, correct, and coherent before archiving.
2
Verification Loop
Claude Code 会话的全面验证系统。
0
Verification Loop
A comprehensive verification system for Claude Code sessions.
1
JSON Validation
Centralized JSON validation for AGENT_SUCCESS_CRITERIA with defensive parsing and injection attack prevention (CVSS 8.2)
3 · bundle
Verify Claims
Find sources for every numerical claim in the draft, add inline hyperlinks, and add internal links to brand-reference articles. Triggered after /draft.
0
Verify
Verify project behavior anchors — compilation, tests, and interaction checks after autonomous runs. NOT the Claude Code built-in /verify (which runs the app to observe a single change working) — this one walks the CLAUDE.md "Features (Behavior Anchors)" list.
8 · bundle
Testing Verification
Testing Verification Skill
0
Verification Loop
Runs a multi-phase verification pipeline including build, type-check, lint, tests, security scan, and diff review to ensure code quality before creating a PR.
226k
Validate
Runs bottom-up type-chain validation across database, hooks, and UI layers, then fixes errors at the failing layer for project health checks before large changes.
1
Verifier Setup
Scaffolds a per-task verification skill for a repo, including a dev-local launcher, a browser driver, and a verification SOP that spawns a sub-agent to drive the app and produce proof.
770 · bundle
Verification Patterns
Provides grep-based patterns to verify that code artifacts are real implementations rather than stubs or placeholders, covering React components, API routes, database schemas, and hooks.
1
Flow Verify
Adversarially verify an implementation against its objective, acceptance criteria, definition of done, and prohibitions using fresh evidence. Use for completion gates, release readiness, or independent verification after implementation and review.
2 · bundle
Verify Changes
Prove code works by running it, not just checking it exists. Verification through execution rather than inspection. Use after writing or modifying code to ensure it actually functions correctly.
3
Verify Before Done
Require fresh evidence before claiming an implementation, fix, build, or test is complete.
4
Outcome Eval
Outcome Eval
18 · bundle
Verification Before Completion
Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always
0
Verification Before Completion
Use before claiming work is complete, fixed, or passing, and before committing or opening a PR - run the actual verification command and read its output before making any success claim.
1
F5
Humanization Quality Verifier - Ensures transformation integrity and quality Validates that humanization preserves meaning, citations, and academic standards Use when: after G6 transformation, before final export, for quality assurance Triggers: verify humanization, check transformation, validate changes
1k