knowledge-sync

Detect outdated skills and generate structured SKILL.md update proposals.

Updated Oct 26, 2025
One-click install
npx skills add https://github.com/discountedcookie/10x-mapmaster --skill knowledge-sync
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: knowledge-sync
Source: https://github.com/discountedcookie/10x-mapmaster/tree/main/.opencode/skills/knowledge-sync
Command: npx skills add https://github.com/discountedcookie/10x-mapmaster --skill knowledge-sync

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill ensures team knowledge stays in sync after refactors or major features by mapping code changes to affected skills and proposing updates.

Core Features & Use Cases

  • Change mapping: Identify affected skills from recent commits.
  • Doc updates: Propose updates to SKILL.md and references.
  • OpenSpec alignment: Trigger updates to maintain consistency with specs.

Quick Start

After a major refactor, run knowledge-sync to map changes to skills and propose necessary updates.

Frequently Asked Questions about knowledge-sync

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

FAQPage Schema
How do I keep documentation in sync after code refactors?

Knowledge-sync identifies code changes from recent commits and maps them to affected skill documentation, automatically proposing SKILL.md updates so your docs stay aligned with refactored patterns and new features without manual tracking.

Can I automatically detect which skills need doc updates after a major feature?

Yes. Knowledge-sync detects changes across your codebase, traces them to specific skills, and generates structured update proposals with references, letting you review and approve changes before applying edits.

What's the best way to maintain OpenSpec alignment when code patterns change?

Knowledge-sync maps code changes to skills and triggers updates that keep documentation and OpenSpec specifications consistent, maintaining coherence across your knowledge base after refactors or new implementations.

How does knowledge-sync identify outdated skill documentation?

It follows a phase-based workflow to detect recent codebase changes, analyze divergence between code and existing skill docs, and flag documentation that no longer reflects current patterns or implementations.

Do I need to manually edit SKILL.md files after running knowledge-sync?

Knowledge-sync prepares structured edit proposals for your review and approval, so you maintain control—you approve proposed changes before they're applied to SKILL.md, preventing unwanted modifications.