preservation-verifier

Verify that rewrites preserve code, frontmatter, quotes, tables, links, paths, and numbers.

5.0k|441|Updated Mar 6, 2026

Search Tags:#markdown #ai writing #quality gate #node #content preservation #diff validation #rewrite verification

Ready to run

npx skills add https://github.com/conorbronsdon/avoid-ai-writing --skill preservation-verifier-conorbronsdon

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: preservation-verifier
Source: https://github.com/conorbronsdon/avoid-ai-writing/tree/main/skills/preservation-verifier
Command: npx skills add https://github.com/conorbronsdon/avoid-ai-writing --skill preservation-verifier-conorbronsdon

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve? Rewrites and file edits can silently damage protected content such as code blocks, YAML frontmatter, blockquotes, tables, URLs, file paths, and numeric details. This Skill deterministically compares an original and a rewritten version and reports whether protected content survived, returning PASS, REVIEW, or FAIL. ## Core Features & Use Cases - Deterministic preservation validation: Runs the bundled Node validator (scripts/validate.js) to check fenced code, frontmatter, blockquotes, tables, inline code, URLs, paths, headings, and numbers between before/after versions. - Residual AI-pattern audit: Compares flagged AI-writing pattern counts before and after a rewrite, with a configurable warn/error residual policy. - Bounded repair loop: Routes failures back to the correct rewrite or edit owner at most once, then stops and reports unresolved errors instead of looping indefinitely. - Use Case: After an AI agent rewrites a Markdown document, supply the original and rewritten text to confirm no code sample, link, or figure was altered before accepting the edit. ## Quick Start Ask the agent to compare the original document and the rewritten version and verify that all protected content survived the rewrite.

Frequently Asked Questions about preservation-verifier

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I verify a rewrite preserved code blocks and frontmatter?▼

Provide the original and rewritten versions and run the bundled validator with node scripts/validate.js --residual-policy warn before.md after.md. It checks fenced code, YAML frontmatter, blockquotes, tables, inline code, URLs, paths, and headings, returning PASS, REVIEW, or FAIL.

What content does the preservation validator check?▼

The validator checks fenced code blocks exactly, YAML frontmatter exactly, blockquote and table content, inline code spans, URLs with AI tracking parameters normalized, filesystem paths, heading count and nesting, and numeric literals. Heading text changes and number changes are warnings, not errors.

Can the verifier run without Node.js execution available?▼

Yes. When Node execution is unavailable, the comparison is performed manually against the same preservation contract and the result is labeled model_only. The Skill never claims the deterministic validator ran unless the host actually executed it.

What happens when verification fails?▼

A FAIL identifies the repair owner based on source kind: returned text goes to the rewriter, a named file goes to the file editor. Only one repair re-entry is allowed within the editing budget; a second failure stops the loop and reports unresolved errors.

Does the validator prove the rewrite is semantically faithful?▼

No. Mechanical preservation checks are separate from semantic fidelity. Meaning, attribution, quantities, negation, and representation details require a separate model-only semantic review, which the Skill reports distinctly from deterministic validator results.