kb-lint

Audit knowledge-base documents against code for orphans, drift, and missing entries.

Updated Mar 26, 2026
One-click install
npx skills add https://github.com/Valyay/vibe-design-kit --skill kb-lint
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: kb-lint
Source: https://github.com/Valyay/vibe-design-kit/tree/main/skills/kb-lint
Command: npx skills add https://github.com/Valyay/vibe-design-kit --skill kb-lint

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Knowledge-base drift and inconsistencies across KB documents can lead to misinformed design decisions and wasted time.

Core Features & Use Cases

  • Detect orphans: items listed in KB but missing from code.
  • Detect drift: details differ between KB and code.
  • Detect missing entries: items in code but not in KB.
  • Generate a designer-friendly remediation plan and a cross-document consistency check.

Quick Start

Run the kb-lint skill on your project to generate a health report and proposed fixes.

Frequently Asked Questions about kb-lint

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

FAQPage Schema
How do I detect documentation drift between my knowledge-base and code?

Detect documentation drift by running an audit across your component-graph, entity-map, screen-inventory, user-flows, and visual-language documents to surface orphans, missing entries, and inconsistencies between your knowledge-base and code.

What is a knowledge-base audit for design files?

A knowledge-base audit identifies orphans, drift, and missing entries across your design documents by comparing them directly against your code to keep the component-graph and visual-language vault accurate.

How do I generate a consistency report for my design system inventory?

Generate a consistency report by running a cross-document audit that checks your screen-inventory and user-flows against code, returning a designer-friendly remediation plan with proposed fixes.

Can I log knowledge-base health status automatically to a markdown file?

Yes, you can log knowledge-base health status automatically to _sync-log.md, which records the audit results and proposed fixes generated from your cross-document consistency check.

What is the best way to find orphaned items listed in my knowledge-base but missing from code?

The best way to find orphaned items is to run an audit that flags entries listed in your knowledge-base documents but missing from your actual codebase, returning them in a structured remediation report.

Does the audit require any external dependencies to check my component-graph?

No, the audit requires no external dependencies to check your component-graph and entity-map, running internally to compare your knowledge-base documents against your code.