Results for “result-verification”

Verifica la reproducibilidad y consistencia de un análisis de datos antes de presentarlo, validando contra la pregunta original y documentando limitaciones.

Verify code changes work by running them. Proves through execution, not just inspection.

Publishes Markdown articles and images into LanceDB via the sf-cli tool, syncs notes, infers missing metadata, and verifies results with local API checks.

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".

Verification-before-completion discipline ensuring all success criteria are met, tests pass, and reviews complete before declaring work done.

Verify tasks marked [X] in tasks.md are implemented, not phantom completions (marked done but backed by missing or dead code).

Verify the article’s factual, product, citation, and link integrity before visual production.

Verify that a change really works before you claim completion

Verifies each step of a rough implementation plan against source code and current documentation, attaching proof and marking steps as verified or unverified.

Enforces running verification commands and confirming output before claiming work is complete, fixed, or passing, to prevent false success claims.

Runs a three-layer verification pipeline on AI-generated output: extracts verifiable claims, finds supporting or contradicting sources via web search, and produces a structured verification report with source links for human review.

Verifies suspected security bugs to eliminate false positives, producing a TRUE POSITIVE or FALSE POSITIVE verdict with documented evidence for each.

Post-merge UAT verification workflow. Walks JIRA reproduce steps, performs comparative audits (Before/After), attaches evidence to JIRA, and transitions status on PASS.

Verify feature, bug, UI, API, mobile, security, or deployment work against acceptance criteria.

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

Verify implementation matches change artifacts. Use when the user wants to validate that implementation is complete, correct, and coherent before archiving.

Guides CAPA effectiveness assessment with verification methods, SMART criteria, and closure requirements.

Enforces running verification commands and confirming output before claiming work is complete, fixed, or passing, ensuring evidence precedes any success claims.

Enforces a verification gate before any completion claim, requiring fresh command output as evidence.

Verify tasks marked [X] in tasks.md are implemented, not phantom completions (marked done but backed by missing or dead code).

EmailVerify API skill. Use when working with EmailVerify for sendCode, checkCode. Covers 2 endpoints.

Verify implementation matches change artifacts. Use when the user wants to validate that implementation is complete, correct, and coherent before archiving.

Claude Code 会话的全面验证系统。

A comprehensive verification system for Claude Code sessions.

Verify the accuracy of claims and statements by extracting individual assertions, identifying authoritative sources, cross-referencing evidence, and assigning confidence-scored verdicts. Use when the user requests fact checking or provides relevant inputs for this workflow.

Centralized JSON validation for AGENT_SUCCESS_CRITERIA with defensive parsing and injection attack prevention (CVSS 8.2)

Find sources for every numerical claim in the draft, add inline hyperlinks, and add internal links to brand-reference articles. Triggered after /draft.

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.

Three-layer verification pipeline for AI output. Extracts verifiable claims, finds supporting or contradicting sources via web search, runs adversarial review for hallucination patterns, and produces a structured verification report with source links for human review.

Verify implemented work meets acceptance criteria — run tests, check PHPCS, validate Blade output, lando phpunit, lando phpcs, lando yarn test, Playwright tests, accessibility check, post-implementation verification, done criteria validation, checklist review, verification phase

Testing Verification Skill

Validates generated SRS documents against IEEE 830-1998, fixing errors and reporting warnings.