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.