Results for “verification-recipe”

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

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

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

Verify that a change really works before you claim completion

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.

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

Integrate verified email retrieval into Android apps using the Credential Manager API and OpenID4VP for secure, OTP-less email verification.

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

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

A comprehensive verification system for Claude Code sessions.

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.

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 a verification gate before any completion claim, requiring fresh command output as evidence.

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

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

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

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

Verify work before committing, pushing, or requesting review

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

Testing Verification Skill

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

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

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

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.

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.

Require fresh evidence before claiming an implementation, fix, build, or test is complete.

Verify references in an academic paper: check whether each BibTeX entry is real, whether in-text citations match the cited paper's actual content, and produce a structured verification report. Use when user says "验证参考文献", "ref verify", "check references", "核实引用", "引用是否正确", or wants to audit citations in a LaTeX manuscript.

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

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.

Plan, debug, tune, evaluate, export, or deploy public Nemotron embedding and reranking retrieval recipes using the current checkout.

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

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

Systematically explores a web application, finds issues, and produces a report with reproduction evidence for each finding.

Runs a multi-phase verification pipeline for Laravel projects including environment checks, linting, static analysis, tests with coverage, security scans, and deployment readiness.