knowledge-updater

Analyze project changes and route updates to the correct knowledge store.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/VinhHung1999/memory-system-plugin --skill knowledge-updater-vinhhung1999
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: knowledge-updater
Source: https://github.com/VinhHung1999/memory-system-plugin/tree/main/plugins/memory-system/skills/knowledge-updater
Command: npx skills add https://github.com/VinhHung1999/memory-system-plugin --skill knowledge-updater-vinhhung1999

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

After significant code changes, knowledge gets stale — CLAUDE.md may reference old build commands, rules may not cover new patterns, or memory/skills may miss important learnings. This skill analyzes changes and routes updates to the correct knowledge store.

Core Features & Use Cases

  • Analyze changes to determine where knowledge should live: CLAUDE.md, .claude/rules/, ~/.claude/memory/, or the skills directory.
  • Route updates automatically to the appropriate store, preserving existing content and avoiding duplication.
  • Coordinate with the memory-system for cross-project lessons or project-specific rules, while keeping workflows lightweight.

Quick Start

Run /knowledge-updater after significant changes to route updates to the correct knowledge store.

Frequently Asked Questions about knowledge-updater

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

FAQPage Schema
How do I update CLAUDE.md and project rules after significant code changes?

To update CLAUDE.md and rules after code changes, analyze the modifications and route the new knowledge to the appropriate store. This ensures references like build commands and coding patterns remain current without duplication.

What is the best way to route code-change learnings to memory or skills directory?

Routing code-change learnings to memory or the skills directory involves analyzing project updates and deploying them to the correct knowledge store. This targets project-specific rules and cross-project lessons while avoiding duplicate entries.

When do I need to update knowledge stores in a development workflow?

You need to update knowledge stores in a development workflow after significant code changes occur. This prevents knowledge from becoming stale when CLAUDE.md references old commands, rules miss new patterns, or memory lacks important learnings.

Does the knowledge updater coordinate with a memory-system for cross-project rules?

Yes, the knowledge updater coordinates with the memory-system for cross-project lessons and project-specific rules. It preserves existing content while maintaining lightweight workflows and routing updates correctly.

How to avoid duplication when updating CLAUDE.md and memory stores?

To avoid duplication when updating CLAUDE.md and memory stores, route updates automatically to the appropriate store after analyzing changes. This preserves existing content and ensures new knowledge is correctly categorized.