kb-update

Synchronize project knowledge base files with recent code changes using git diffs.

2|2|Updated Mar 17, 2026
One-click install
npx skills add https://github.com/mathiasbourgoin/roster --skill kb-update-mathiasbourgoin
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: kb-update
Source: https://github.com/mathiasbourgoin/roster/tree/main/.opencode/skills/kb-update
Command: npx skills add https://github.com/mathiasbourgoin/roster --skill kb-update-mathiasbourgoin

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

After code changes, project knowledge bases often drift out of sync, leading to outdated specifications, missing documentation for new features, and undetected contradictions between implemented code and written requirements. Manually updating the KB is time-consuming and risks accidentally weakening existing specs or missing critical inconsistencies.

Core Features & Use Cases

  • Automated Change Detection: Uses git diffs to identify recently modified source files and extract relevant changes.
  • Spec Compliance Checking: Flags any code that contradicts existing KB specifications instead of altering specs to match incorrect code.
  • Structured KB Updates: Adds new entries for new features, refines existing entries for clarified concepts, and updates cross-references between related documentation.
  • Ambiguity Auditing: Runs checks to ensure all KB entries use defined terms, avoid vague language, and contain no internal contradictions.
  • Use Case: After merging a new user authentication API, use this Skill to automatically add the endpoint's documentation to the KB, add new terms like "OAuth2 refresh token" to the glossary, and verify no existing access control specs are violated by the new code.

Quick Start

Use the kb-update skill to sync the project knowledge base with all code changes from the last 5 commits.

Frequently Asked Questions about kb-update

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

FAQPage Schema
How do I sync a knowledge base with recent code changes after a merge?

To sync a knowledge base with recent code changes, you can use git diffs to identify modified source files and automatically update documentation entries. This process adds new feature specs, refines existing concepts, and updates cross-references without weakening original technical specifications.

How do I prevent documentation drift when updating technical specs?

Preventing documentation drift requires flagging code that contradicts existing KB specifications instead of altering specs to match incorrect code. Strict guardrails ensure written requirements are enforced during post-merge updates, maintaining spec integrity while adding new glossary terms.

What is an ambiguity audit for technical documentation?

An ambiguity audit checks knowledge base entries to ensure they use defined terms, avoid vague language, and contain no internal contradictions. This maintains clarity and consistency across technical specification repositories after applying code changes.

Can I check spec compliance automatically using git diff?

Yes, spec compliance checking uses git diffs from recent commits to automatically flag any code that contradicts existing KB specifications. This ensures implemented code aligns with written requirements without manually reviewing every modified file.

What is the best way to update technical specifications without weakening existing requirements?

The best way to update technical specifications without weakening requirements is enforcing strict guardrails that flag contradictory code rather than altering existing specs. This approach adds new entries for new features while preserving the original validation rules.