re-read

Audit post-edit changes for contradictions and stale references.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/BoChao1Zhang/dotfiles --skill re-read
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: re-read
Source: https://github.com/BoChao1Zhang/dotfiles/tree/main/dot_codex/skills/re-read
Command: npx skills add https://github.com/BoChao1Zhang/dotfiles --skill re-read

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Post-edit audit checks identify inconsistencies, contradicting statements, and hallucinated references in the region around edits, ensuring documentation and code stay accurate after changes.

Core Features & Use Cases

  • Read, Grep, and Glob across a ±30-line window around edits to validate content.
  • Check for contradictions, hallucinated references, stale information, and tonal drift.
  • Extend analysis window as needed to improve context and accuracy.

Quick Start

Invoke the audit workflow on the edited region to validate the changes against the checklist.

Frequently Asked Questions about re-read

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

FAQPage Schema
How do I check for hallucinated references and contradictions after editing a document?

Post-edit audit checks validate edited regions against a consistency and accuracy checklist. They scan a ±30-line window around edits using Read, Grep, and Glob to detect hallucinated references, contradictions, stale information, and tonal drift across referenced files.

What is a post-edit consistency audit for code and documentation?

A post-edit consistency audit is a validation workflow that reviews recent changes within a configurable line window around edits. It chains Read, Grep, and Glob operations to identify contradicting statements, stale information, and tonal drift in code or documents.

How do I audit recent code changes for stale information and tonal drift?

Invoke an audit workflow on the edited region to validate changes against a checklist. The workflow extends analysis across a ±30-line window around edits, chaining Read, Grep, and Glob to validate content and check for stale information or tonal drift.

Can I adjust the context window size when auditing edited files?

Yes, the analysis window size is configurable. You can extend the ±30-line window as needed to improve context and accuracy when chaining Read, Grep, and Glob across referenced files to validate content.

Does the post-edit audit check work across multiple referenced files?

Yes, the audit chains Read, Grep, and Glob across referenced files to validate content. It checks for contradictions, hallucinated references, stale information, and tonal drift within the configured window around edits.

Why do I need post-edit checks to prevent documentation inconsistencies?

Post-edit checks are needed to identify inconsistencies, contradicting statements, and hallucinated references in the region around edits, ensuring documentation and code stay accurate after changes.