brewdoc:auto-sync

Synchronize documentation files by tracking frontmatter and detecting stale content.

30|2|Updated Jan 24, 2026
One-click install
npx skills add https://github.com/kochetkov-ma/claude-brewcode --skill brewdoc-auto-sync
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: brewdoc:auto-sync
Source: https://github.com/kochetkov-ma/claude-brewcode/tree/main/brewdoc/skills/auto-sync
Command: npx skills add https://github.com/kochetkov-ma/claude-brewcode --skill brewdoc-auto-sync

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the process of keeping documentation files (skills, agents, markdown) up-to-date across your project or globally, preventing stale information and saving manual synchronization effort.

Core Features & Use Cases

  • Automatic Tracking: Identifies and tracks documentation files with specific frontmatter.
  • Stale Content Detection: Alerts you to documentation that hasn't been updated within a defined interval.
  • Intelligent Updates: Researches code and verifies paths/URLs to update documentation automatically.
  • Use Case: Ensure your SKILL.md files accurately reflect the current functionality of your code by automatically syncing them with their respective codebases.

Quick Start

Run /brewdoc:auto-sync status to see what documentation is tracked and what might be stale.

Frequently Asked Questions about brewdoc:auto-sync

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

FAQPage Schema
How do I automatically sync markdown documentation with my codebase?

You can sync markdown documentation automatically by running the global sync mode, which tracks files with specific frontmatter, identifies stale content based on defined sync intervals, and updates documentation by researching code and verifying paths and URLs.

How does stale content detection work for markdown files?

Stale content detection for markdown files works by tracking documentation with specific frontmatter and alerting you when files have not been updated within a defined sync interval, ensuring your project information never becomes outdated.

What is the best way to check if my project documentation needs updating?

The best way to check if project documentation needs updating is to run a status check mode, which identifies all tracked documentation files and alerts you to any content that has become stale based on configured sync intervals.

Can I sync documentation for an individual file instead of the whole project?

Yes, you can sync documentation for an individual file or folder instead of the whole project, because the Skill supports multiple synchronization modes including global sync, project sync, and individual file or folder synchronization.

How do agents and skills documentation stay up to date across a project?

Agents and skills documentation stay up to date across a project through intelligent updates that automatically research code and verify paths and URLs, preventing stale information and saving manual synchronization effort across your entire codebase.