agentleFS
lbb00lbb00/ai-rules-sync/.claude/skills/update-knowledge-base/SKILL.md

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

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
  1. Very specific:

    Check if KNOWLEDGE_BASE.md exists

    line 20
  2. Distinctive:

    If not, create it with proper structure

    line 21
  3. Distinctive:

    If exists, identify sections needing updates

    line 22
  4. Distinctive:

    Architecture: Update if new adapters or core components added

    line 25
  5. Distinctive:

    Features: Document new CLI commands or options

    line 26
  6. Distinctive:

    API Changes: Document breaking changes or deprecations

    line 28
  7. Distinctive:

    Ensure examples are runnable

    line 32
  8. Distinctive:

    Check that all documented features exist

    line 33
  9. Distinctive:

    Use consistent markdown formatting

    line 36
  10. Distinctive:

    After running this skill:

    line 70

“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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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

  1. Analyze Recent Changes
    • Review git diff or recent commits
    • Identify new adapters, commands, or features
    • Note architectural changes or new patterns
  2. Read Current Knowledge Base
    • Check if KNOWLEDGE_BASE.md exists
    • If not, create it with proper structure
    • If exists, identify sections needing updates
  3. 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
  4. Verify Accuracy
    • Cross-reference with actual source code
    • Ensure examples are runnable
    • Check that all documented features exist
  5. 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 changes

Output

After running this skill:

  • KNOWLEDGE_BASE.md is created or updated
  • Changes reflect current codebase state
  • Documentation is accurate and complete

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.