docs-sync

Compare main branch features against current docs to generate gap reports.

Updated Feb 23, 2026
One-click install
npx skills add https://github.com/sisyphus1212/codex-fusion-starter-template --skill docs-sync-sisyphus1212
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: docs-sync
Source: https://github.com/sisyphus1212/codex-fusion-starter-template/tree/main/scaffold/.agents/skills/docs-sync
Command: npx skills add https://github.com/sisyphus1212/codex-fusion-starter-template --skill docs-sync-sisyphus1212

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Identify documentation gaps and inaccuracies by comparing the main branch features and configuration options against the current docs structure, then propose targeted improvements.

Core Features & Use Cases

  • Document coverage assessment across docs/ and docs/ref.
  • Detect missing option mentions, env vars, and config details.
  • Generate actionable reports with evidence and suggested edits for English docs under docs/** while preserving translated docs.

Quick Start

Run the docs-sync workflow to generate a gap report and proposed edits for English docs under docs/**, excluding translations.

Frequently Asked Questions about docs-sync

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

FAQPage Schema
How do I audit my documentation to find missing configuration options?

To audit documentation gaps, you compare your main branch configuration options against the current docs structure to detect missing options and generate a structured gap analysis report with evidence and suggested edits.

What is documentation gap analysis and how does it work with a docs directory?

Documentation gap analysis inventories doc items by comparing the current branch against main, detecting missing option mentions and environment variables, and outputting a structured report with actionable recommendations.

How do I generate an actionable report for missing environment variables in docs?

You generate an actionable report by analyzing your docs directory against the main branch to detect missing env vars, outputting a Docs Sync Report with evidence and proposed edits for English docs.

Does this documentation audit apply to translated docs in my project?

No, this documentation audit specifically targets English docs under docs/**. It analyzes the current branch versus main while preserving and excluding translated docs from the generated gap analysis report.

What's the best way to check document coverage across docs and reference directories?

The best way to check document coverage is to run a gap analysis workflow that inventories doc items across docs/ and docs/ref, comparing the current branch to main to detect missing configuration details.