docs-sync

Validates Rust CLI READMEs and source code for documentation drift.

18|Updated Jun 26, 2025
One-click install
npx skills add https://github.com/shutootaki/gwm --skill docs-sync-shutootaki
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: docs-sync
Source: https://github.com/shutootaki/gwm/tree/main/.claude/skills/docs-sync
Command: npx skills add https://github.com/shutootaki/gwm --skill docs-sync-shutootaki

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill ensures that your project's documentation stays perfectly synchronized with its source code, preventing outdated information and user confusion.

Core Features & Use Cases

  • Drift Detection: Identifies discrepancies between CLI arguments, configuration types, and their documentation in README files.
  • Cross-Language Consistency: Verifies that English and Japanese READMEs maintain structural parity.
  • Environment Variable Check: Ensures all relevant environment variables are documented.
  • Use Case: After updating a CLI command's arguments, use this Skill to automatically check if the help text and README documentation have been updated accordingly, flagging any inconsistencies before a release.

Quick Start

Run the docs-sync skill to check for documentation drift in the project.

Frequently Asked Questions about docs-sync

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

FAQPage Schema
How do I check documentation consistency between Rust source code and README files?

Documentation drift occurs when source code definitions change but README files do not. You detect this drift by parsing Rust source files and Markdown documents to identify discrepancies in commands, options, and configuration fields.

How do I detect documentation drift in a Rust CLI project before release?

Detect documentation drift in a Rust CLI project by validating that CLI arguments, configuration types, and environment variables match their documented representations in English and Japanese READMEs before a release.

Can I verify cross-language README parity for English and Japanese documentation?

Yes, you can verify cross-language consistency by checking that English and Japanese READMEs maintain structural parity, ensuring that CLI arguments and configuration types are identically documented across both languages.

Does this documentation sync tool check for undocumented environment variables?

Yes, the documentation sync tool includes an environment variable check that parses Rust source files to ensure all relevant environment variables are properly documented in the README files.

What is the best way to automate CLI argument validation against help text?

The best way to automate CLI argument validation is to run a script that parses Rust source files and Markdown documents to report discrepancies between the actual command line options and their help text documentation.

What limitations exist when syncing markdown documentation for Rust projects?

A limitation is that the sync process specifically requires parsing Rust source files and Markdown documents, meaning it is tailored for Rust CLI projects and may not support other programming languages or documentation formats.