kb-lint

Health-check knowledge bases for contradictions, stale claims, and orphan files.

41|6|Updated Jul 12, 2025
One-click install
npx skills add https://github.com/SteveGJones/ai-first-sdlc-practices --skill kb-lint-stevegjones
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: kb-lint
Source: https://github.com/SteveGJones/ai-first-sdlc-practices/tree/main/plugins/sdlc-knowledge-base/skills/kb-lint
Command: npx skills add https://github.com/SteveGJones/ai-first-sdlc-practices --skill kb-lint-stevegjones

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Health-check the project knowledge base to surface contradictions between files, stale claims that newer sources have superseded, orphan files with no inbound cross-references, important concepts mentioned but lacking their own page, missing cross-references, and data gaps. Returns a structured report; does not auto-fix.

Core Features & Use Cases

  • Continuous validation of KB content to detect logical drift, orphan accumulation, and gaps between sources.
  • Cross-reference enrichment and maintenance planning for knowledge-heavy projects.
  • Use Case: Run kb-lint after ingest to ensure the knowledge base remains consistent across domains before publishing.

Quick Start

Run the knowledge base linter over your library to generate a health report and highlight actionable gaps.

Frequently Asked Questions about kb-lint

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

FAQPage Schema
How do I validate my knowledge base for contradictions and stale claims?

Knowledge base validation automates health-checks to surface contradictions, stale claims, and data gaps across your library. It generates a structured report highlighting logical drift and actionable maintenance tasks without applying auto-fixes.

What is the best way to detect orphan files and missing cross-references in documentation?

Detecting orphan files and missing cross-references requires cross-reference analysis across the entire knowledge base. The linter identifies files with no inbound references and important concepts lacking dedicated pages for maintenance planning.

Can I run documentation quality checks on a scoped subset of my knowledge base?

Documentation quality checks can be scoped to specific subsets of the knowledge base library. Optional flags for scope, strict-layer, and strict-confidence allow targeted cross-domain inconsistency detection and compliance validation.

Does knowledge base linting support CI-like validation workflows?

Knowledge base linting supports CI-like validation by automating continuous health-checks after content ingest. This ensures the library remains consistent across domains before publishing, returning layer and confidence compliance results.

How do I fix data gaps and logical drift found during knowledge base health-checks?

Fixing data gaps and logical drift found during health-checks requires manual intervention or the optional auto-fix workflow flag. The linter surfaces the issues and outputs a structured report but does not automatically resolve them by default.