Does it automatically commit changes to my repository?

The skill analyzes changes and updates the files, but it provides a summary and asks for user confirmation before suggesting a git commit.

Does this skill document planned or future features?

No, the skill explicitly ignores planned states. It only documents features and modules that have been successfully implemented in the codebase to prevent documentation drift.

When should I run the sync-docs skill?

You should run it at the end of a development session, after major architectural changes, or whenever you complete a feature that needs to be documented for the team.

What documentation files does this skill manage?

It manages specific files in the .claude/docs/ directory, including ARCHITECTURE.md, CONVENTIONS.md, MODULES.md, and REQUIREMENTS.md.

Documentation Sync

Name: Documentation Sync
Author: Central-MakeUs

byCentral-MakeUs

•

Aprendizaje y Documentación

Automates the synchronization and maintenance of project documentation based on actual code implementations.

The Documentation Sync skill streamlines the developer workflow by automatically updating core project files within the .claude/docs/ directory. It analyzes session changes, code diffs, and architectural shifts to ensure that ARCHITECTURE.md, CONVENTIONS.md, MODULES.md, and REQUIREMENTS.md accurately reflect the current state of the codebase. By enforcing a strict rule that only implemented features are documented, it eliminates stale or speculative documentation, providing developers and AI agents with a reliable, up-to-date source of truth for the project's structure and standards.

Características Principales

01Seamless integration with AGENTS.md to provide context for AI coding assistants

02Standardized Markdown templates for consistent project-wide documentation

03Implementation-based updates that exclude planned or speculative features

042 GitHub stars

05Smart analysis of session history and git diffs to identify changes

06Automatic synchronization of architecture, conventions, and module documentation

Casos de Uso

01Maintaining current code conventions and naming rules after a refactoring session

02Updating project architecture and module docs after completing a major feature

03Syncing documentation at the end of a development session for accurate handovers

Características Principales

01Seamless integration with AGENTS.md to provide context for AI coding assistants

02Standardized Markdown templates for consistent project-wide documentation

03Implementation-based updates that exclude planned or speculative features

042 GitHub stars

05Smart analysis of session history and git diffs to identify changes

06Automatic synchronization of architecture, conventions, and module documentation

Casos de Uso

01Maintaining current code conventions and naming rules after a refactoring session

02Updating project architecture and module docs after completing a major feature

03Syncing documentation at the end of a development session for accurate handovers