Results for “citation-verification”

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

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.

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

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

A comprehensive verification system for Claude Code sessions.

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

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

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

Gate anti-alucinacao do plugin civel: valida vigencia e existencia de dispositivo, sumula, tese, tema e enunciado ANTES de qualquer citacao entrar em peca. Cruza com context/ (CPC/CC + reformas + jurisprudencia) e, na duvida, exige checagem ao vivo (fetch real) ou bloqueia. Integra o guard global anti-alucinacao-juridica. Use antes de citar qualquer fundamento, ou quando o operador disser valida essa jurisprudencia, esse artigo existe, essa sumula esta vigente, esse tema/acordao existe, confere essa ementa, antes de citar, esse dispositivo ainda esta em vigor, checa esse fundamento.

Use when sources must stay traceable across sessions and years, when each reference needs a passport recording where it was found, how it was verified, and where it is cited, or when a draft needs a cited-but-unverified sweep before submission.

Verify that a change really works before you claim completion

Bind content to live product proof and an accountable author voice.

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.

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

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.

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

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.

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.