Will it overwrite my manual documentation?

No. The skill respects 'auto-sync' flags in your configuration, allowing you to choose whether to rewrite sections entirely or preserve hand-written content while updating subsections.

How does it handle security during probes?

The skill includes a pre-dispatch safety gate that filters out any destructive commands (like rm, delete, or force) before they are executed by the probing agent.

Does it require specific MCP tools?

While it can run in static-only mode, it optionally uses episodic-memory and private-journal MCP tools to enrich documentation with real-world usage patterns and technical insights.

How does the 'Live Probe' verification work?

The skill extracts behavioral claims from your docs, generates safe CLI commands to test those claims, and runs them to ensure the software actually behaves as described.

What is E2E Doc Sync?

It is a specialized Claude Code skill that identifies gaps between your E2E plugin code and its documentation, automatically writing updates and verifying accuracy through functional probes.

E2E Documentation Sync & Verifier

Name: E2E Documentation Sync & Verifier
Author: iamcxa

byiamcxa

•

Learning & Documentation

Syncs and verifies E2E plugin documentation using diff-aware scanning, history enrichment, and live behavior probing.

E2E Doc Sync is a sophisticated documentation maintenance tool designed to keep technical guides in lockstep with codebase changes. By performing diff-aware scans of skills and agents, it identifies critical gaps where features exist without documentation. The skill goes beyond simple writing by enriching content with usage history from MCP tools and performing 'Live Probes'—executing safe CLI commands to verify that documentation claims match actual software behavior. It is an essential utility for developers maintaining complex plugin ecosystems who need to ensure their documentation is always accurate, complete, and functionally verified.

Key Features

013 GitHub stars

02Behavioral claim verification through automated live CLI probes

03Diff-aware documentation gap scanning and orphan detection

04Automated documentation generation with style calibration

05Self-updating source-to-doc maps and probe configurations

06History enrichment using episodic memory and private journal context

Use Cases

01Identifying undocumented features that are frequently used in historical sessions

02Automatically updating E2E testing guides after adding new agent skills

03Verifying that CLI examples in README files remain functional after updates

Key Features

013 GitHub stars

02Behavioral claim verification through automated live CLI probes

03Diff-aware documentation gap scanning and orphan detection

04Automated documentation generation with style calibration

05Self-updating source-to-doc maps and probe configurations

06History enrichment using episodic memory and private journal context

Use Cases

01Identifying undocumented features that are frequently used in historical sessions

02Automatically updating E2E testing guides after adding new agent skills

03Verifying that CLI examples in README files remain functional after updates