sync-docs

Detect git changes and patch business/architecture docs accordingly.

Updated Mar 6, 2026
One-click install
npx skills add https://github.com/nand1234/Agentic-workflow-builder --skill sync-docs-nand1234
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sync-docs
Source: https://github.com/nand1234/Agentic-workflow-builder/tree/main/ai-dev-worflow/.claude/skills/sync-docs
Command: npx skills add https://github.com/nand1234/Agentic-workflow-builder --skill sync-docs-nand1234

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Re-enriches living documentation after a ticket or feature lands, preventing drift and misalignment.

Core Features & Use Cases

  • Detect changes from recent commits and identify updated sections across docs.
  • Patch docs/business/workflows.md and docs/architecture files to reflect new changes.
  • Preserve human-authored descriptions while surfacing gaps and suggestions for improvement.

Quick Start

Update docs after a feature lands by running the sync-docs skill on the current branch to refresh impacted sections.

Frequently Asked Questions about sync-docs

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

FAQPage Schema
How do I sync documentation with code changes after a feature lands?

You can sync documentation by detecting changes from recent commits and selectively patching referenced business, architecture, and workflow docs to reflect the new code updates.

What is the best way to prevent documentation drift after updating architecture notes?

Preventing documentation drift involves detecting code changes via git diff and selectively patching impacted architecture notes and workflow references to align with the latest updates.

How does selective patching work for living docs when code changes occur?

Selective patching detects updated sections via git, patches the referenced business and architecture docs, and preserves human-authored descriptions while surfacing gaps and suggestions.

Can I update multiple workflow and business docs across frontend and backend domains at once?

Yes, you can align multiple docs across frontend and backend domains by detecting git changes and selectively patching workflow references and business documentation to reflect the updates.

Does syncing docs preserve my manually written descriptions and notes?

Syncing docs preserves human-authored descriptions while identifying updated sections, applying patches for new changes, and reporting what was changed along with any new documentation gaps.

What limitations exist when using git diff to update architecture documentation?

Using git diff to update architecture documentation relies on detecting commit changes, so it requires a current branch with recent commits to accurately patch docs and report gaps.