Does it modify my files without permission?

No. The skill generates a diff of proposed changes and requires explicit user approval (yes/no) before any file is updated or committed.

When does this skill trigger?

The protocol only executes once a development track has reached completed status and the implementation command has finished all tasks.

Which specific files are managed by this skill?

It synchronizes three core files: product.md, tech-stack.md, and product-guidelines.md within the conductor directory.

Can it handle branding or guideline changes?

Yes, but it includes a high-sensitivity warning system for product-guidelines.md, requiring strict conditions to be met before suggesting changes to core identity.

Does it integrate with Git?

Yes, after changes are approved and applied, the skill automatically stages the modified files and creates a standardized commit message.

Project Context Synchronizer

Name: Project Context Synchronizer
Author: vinothpandian

byvinothpandian

•

Content Management

Maintains project-level documentation by automatically synchronizing product specs and technical stacks after feature completion.

About

The Context Synchronization skill solves the problem of documentation rot by ensuring high-level project files stay aligned with the actual state of the codebase. When a development track is completed, this skill analyzes the changes to determine if updates are required for the product description, technology stack, or core guidelines. It provides an interactive workflow where users review proposed diffs before changes are applied and committed to the repository, maintaining a reliable single source of truth for the entire project context.

Key Features

Support for product, tech-stack, and guideline files
1 GitHub stars
Interactive diff-based update proposals
Automated documentation impact analysis
Strict safety protocols for branding guidelines
Automated Git staging and standardized commits

Use Cases

Refreshing the product.md overview after launching a major feature
Updating the tech-stack.md after introducing new libraries or services
Ensuring project documentation stays current during rapid development cycles

About

Key Features

Support for product, tech-stack, and guideline files
1 GitHub stars
Interactive diff-based update proposals
Automated documentation impact analysis
Strict safety protocols for branding guidelines
Automated Git staging and standardized commits

Use Cases

Refreshing the product.md overview after launching a major feature
Updating the tech-stack.md after introducing new libraries or services
Ensuring project documentation stays current during rapid development cycles