docs-sync

Reconcile documentation with branch code changes before PR submission.

1|Updated Jul 5, 2026

Search Tags:#code documentation #commit hooks #branch diff #doc reconciliation #intent-oracle

Ready to run

npx skills add https://github.com/stoodder/materia --skill docs-sync-stoodder

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: docs-sync
Source: https://github.com/stoodder/materia/tree/main/plugins/materia/skills/docs-sync
Command: npx skills add https://github.com/stoodder/materia --skill docs-sync-stoodder

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill automatically reconciles and updates documentation with the branch's aggregate code changes before the PR is submitted, reducing manual errors and ensuring doc accuracy.

Core Features & Use Cases

Branch Diff Reconciliation: Compares code changes with the branch's state to identify discrepancies.
Cross-Cutting Documentation Update: Updates CLAUDE.md, README index, surface-map, and glossary with branch changes.
Intent-Oracle Handling: Corrects doc inconsistencies with code without manual intervention.
Doc Change Summary: Commits changes with a summary for audit trails.
Use Case: After implementing a feature, the Skill can automatically update related documentation sections and maintain consistency between code and documentation.

Quick Start

Run the 'docs-sync' command with the branch diff to reconcile and update documentation.

Frequently Asked Questions about docs-sync

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

FAQPage Schema

How do I automatically update documentation to match code changes before submitting a pull request?▼

To update documentation before a pull request, you can reconcile docs with branch code changes by analyzing diffs and applying updates through commit hooks. This ensures doc accuracy and reduces manual errors before PR submission.

How do I keep README and glossary entries consistent with branch diff modifications?▼

Keeping README and glossary entries consistent involves cross-cutting documentation updates that compare branch state with code modifications. This process automatically identifies discrepancies and updates related doc sections to maintain consistency.

What is intent-oracle discrepancy handling in code documentation reconciliation?▼

Intent-oracle discrepancy handling in code documentation reconciliation is the process of correcting doc inconsistencies with code automatically. It analyzes branch diffs against intent-oracle rules to resolve mismatches without manual intervention.

Can I use commit hooks to enforce documentation updates when reconciling branch diffs?▼

Yes, commit hooks can enforce documentation updates during branch diff reconciliation. The Skill applies changes through docs standards and commit hooks, committing doc updates with a summary for audit trails before PR submission.

What is the best way to maintain a documentation tree across aggregate code changes?▼

The best way to maintain a documentation tree across aggregate code changes is to automatically reconcile the docs directory with branch state. This handles cross-cutting updates to surface maps and glossaries, ensuring doc accuracy.

Why does my documentation drift out of sync with my branch code changes?▼

Documentation drifts out of sync with branch code changes when manual updates are missed during feature implementation. Reconciling the docs tree with branch diffs before PR submission corrects these inconsistencies and maintains accuracy.