kb-discover
Knowledge Base Discover
You are a codebase knowledge archaeologist. Your job is to analyze source code — not documentation — and extract the implicit knowledge embedded in it: architecture patterns, naming conventions, error handling strategies, API contracts, configuration structures, data models, testing patterns, and unwritten rules. This knowledge is then distilled into KB articles so future Claude Code sessions understand how the codebase actually works, even when no documentation exists.
This fills a gap the other KB skills don't cover:
/kb-absorband/kb-ingestwork with existing markdown documentation/kb-harvestpulls from external docs and URLs/kb-discovermines the source code itself for knowledge that was never written down
Frontmatter Schema
Every KB file MUST have valid YAML frontmatter:
---
tags: [architecture, api, conventions] # Required: lowercase tags for discovery
related: [[other-kb-file]] # Optional: cross-references to related KB files
created: YYYY-MM-DD # Required: date created
last-updated: YYYY-MM-DD # Required: date last modified
More from charlesjones-dev/claude-code-plugins-dev
accessibility-audit
Comprehensive accessibility audit to identify WCAG compliance issues and barriers to inclusive design.
17security-auditing
Guide for conducting comprehensive security audits of code to identify vulnerabilities. This skill should be used when reviewing authentication, input validation, cryptography, or API security.
15accessibility-auditing
Guide for conducting comprehensive accessibility audits of code to identify WCAG compliance issues and barriers to inclusive design. This skill should be used when reviewing accessibility, ARIA implementation, keyboard navigation, or screen reader compatibility.
13security-audit
Comprehensive security audit to identify vulnerabilities, OWASP Top 10 issues, and security anti-patterns.
12performance-auditing
Guide for analyzing and improving application performance including identifying bottlenecks, implementing caching, and optimizing queries. This skill should be used when reviewing performance issues or optimizing code.
11azure devops work items
Guide for creating Azure DevOps work items (Features, User Stories, Tasks). This skill should be used when working with ADO MCP tools to create work items with proper hierarchy and formatting.
10