update-knowledge-base
Skill37 starsChanged 9 months agoUnlicenseView on GitHub
Analyze code changes and update KNOWLEDGE_BASE.md with architectural and feature changes.
4 other projects use a version of this.
Adopted by
Most recently taken up by
- SamAmco/track-and-graphtheir own version, first seen Oct 9, 2026
- moorage/fullwelltheir own version, first seen Jul 31, 2026
- huytieu/COG-second-braintheir own version, first seen Jul 30, 2026
- serpeigd/TrainFittertheir own version, first seen Jul 27, 2026
Other versions4 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 4
- huytieu/COG-second-brain★ 1.3ksame name
- SamAmco/track-and-graph★ 658same name
- serpeigd/TrainFitter★ 2same name
- moorage/fullwell★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository8 other files it gives its agents.
- AGENTS.mdAGENTS.md
- .claude/CLAUDE.mdCLAUDE.md
- .cursor/rules/knowledge-base/RULE.mdCursor rule
- .cursor/rules/project/RULE.mdCursor rule
- new-adapterSkill
- summarize-sessionSkill
- sync-readmeSkill
- update-docsSkill
The file
We split this skill into the rules it gives an agent
10 rules. 0 are common, 9 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 4 edited versions we read keep these.
9
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 20
Check if KNOWLEDGE_BASE.md exists
- Distinctive: line 21
If not, create it with proper structure
- Distinctive: line 22
If exists, identify sections needing updates
- Distinctive: line 25
Architecture: Update if new adapters or core components added
- Distinctive: line 26
Features: Document new CLI commands or options
- Distinctive: line 28
API Changes: Document breaking changes or deprecations
- Distinctive: line 32
Ensure examples are runnable
- Distinctive: line 33
Check that all documented features exist
- Distinctive: line 36
Use consistent markdown formatting
- Distinctive: line 70
After running this skill:
“Common” is measured: kept by at least 6 in 10 of the 4 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Update Knowledge Base
Purpose
Automatically analyze recent code changes and update the project's knowledge base documentation to reflect current architecture, features, and conventions.
Instructions
- Analyze Recent Changes
- Review git diff or recent commits
- Identify new adapters, commands, or features
- Note architectural changes or new patterns
- Read Current Knowledge Base
- Check if KNOWLEDGE_BASE.md exists
- If not, create it with proper structure
- If exists, identify sections needing updates
- Update Sections
- Architecture: Update if new adapters or core components added
- Features: Document new CLI commands or options
- Conventions: Note any new coding patterns established
- API Changes: Document breaking changes or deprecations
- Verify Accuracy
- Cross-reference with actual source code
- Ensure examples are runnable
- Check that all documented features exist
- Format Consistently
- Use consistent markdown formatting
- Include code examples where helpful
- Maintain table format for command references
Knowledge Base Structure
# AI Rules Sync - Knowledge Base
## Architecture Overview
- Adapter system description
- CLI layer structure
- Config management
## Supported Tools
| Tool | Types | Source Dir | Target Dir |
## Commands Reference
| Command | Description | Example |
## Adapter Implementation
- How to add new adapters
- Required interfaces
## Configuration
- ai-rules-sync.json structure
- Local/private rules
## Changelog
- Recent significant changesOutput
After running this skill:
- KNOWLEDGE_BASE.md is created or updated
- Changes reflect current codebase state
- Documentation is accurate and complete
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

