Results for “formal-verification”

Verify that a change really works before you claim completion

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

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

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

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

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

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

Verifies data structures, files, YAML blocks, or agent output against their defined schema, producing a pass/fail report with actionable fix instructions.

A comprehensive verification system for Claude Code sessions.

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.

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.

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

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

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

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.

Proofreads academic writing for grammar, style consistency, jargon clarity, and formal tone

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.

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

Plan structure validation, phase completeness checks, reference integrity verification, and artifact existence confirmation. Provides the structured verification layer ensuring GSD artifacts are well-formed and complete.

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

Validates observable behavior of apps, CLIs, APIs, and generated artifacts against a prewritten contract without inspecting source code.

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

Imported skill __init__ from anthropic

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.

Validate whether an OSS tool is worth building through staged namespace, existing-solution, and feasibility review

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.

Prove a feature works by delegating verification to an independent sub-agent that drives the real app, then open a pull request with the proof.

Drafts attorney-supervised, state-compliant U.S. Advance Health Care Directives that appoint health care agents, resolve the HIPAA access gap, and record clinically usable treatment preferences. Enforces state-law verification for execution formalities, statutory forms, and special limitations. Addresses adversarial risks from family disputes and institutional challenges. Use when drafting advance directives, health care proxies, living wills, health care powers of attorney, HIPAA medical authorizations, or end-of-life planning documents.