Validate and enforce KB documentation formats, completeness, and integrity. Checks recent docs (uncommitted or last N commits) against KB standards. CHECKS PERFORMED: 1. FORMAT - Documents follow required templates (headers, sections) 2. COMPLETENESS - Tickets/issues have all required files (1-5) 3. INTEGRITY - All tickets in index.md, phases in roadmap.md 4. PATTERNS - Have Status: open|resolved 5. NAMING - Files follow conventions (verb-noun, feat-, comp-, etc.) Use when: - Before committing KB docs - After creating tickets/issues - Periodic maintenance - User says "lint kb", "check docs", "validate kb"
Validates KB documentation against standards for format, completeness, and integrity. Checks recent docs or all files for required templates, ticket files, index consistency, and roadmap alignment.
/plugin marketplace add jayprimer/pmc-marketplace/plugin install jayprimer-pmc-plugins-pmc@jayprimer/pmc-marketplaceThis skill inherits all available tools. When active, it can use any tool Claude has access to.
Validate and enforce KB documentation formats, completeness, and integrity.
ALWAYS run /pmc:kb first to understand KB structure and formats.
| Mode | Scope | Command |
|---|---|---|
| Recent | Uncommitted + last 3 commits | /lint-kb (default) |
| Full | All KB docs | /lint-kb full |
| Tickets | Only tickets/issues | /lint-kb tickets |
use /pmc:kb first.
# Uncommitted changes
git status --porcelain .pmc/docs/
# Recently committed (last 3)
git log -3 --name-only --pretty=format: -- .pmc/docs/ | sort -u
Glob: .pmc/docs/**/*.md
Each ticket/issue directory MUST have these files:
| File | Required | Purpose |
|---|---|---|
1-definition.md | Always | What: scope, success criteria |
2-plan.md | Always | How: steps, decisions |
3-spec.md | Always* | TDD: tests, edge cases |
4-progress.md | In progress | Log: TDD cycles, notes |
5-final.md | On completion | Done: status, learnings |
*3-spec.md may be minimal for trivial tickets (TDD: no in constraints).
Glob: .pmc/docs/tickets/T*/
For each directory:
5-final.md has Status: COMPLETE or Status: BLOCKED## Ticket Completeness
| Ticket | 1-def | 2-plan | 3-spec | 4-prog | 5-final | Status |
|--------|-------|--------|--------|--------|---------|--------|
| T00021 | OK | OK | OK | OK | OK | COMPLETE |
| T00022 | OK | OK | MISSING| - | - | In Progress |
Read: .pmc/docs/tickets/index.md
Glob: .pmc/docs/tickets/T*/
Check:
T*/ directory has entry in index.mdT0000N Brief Title (one per line)Read: .pmc/docs/3-plan/roadmap.md
Check:
Critical: Every ticket in tickets/ (not archived) MUST be in roadmap.md - whether as a single item or within a phase.
## Index Integrity
### tickets/index.md
- Missing entries: T00023, T00024
- Orphan entries: none
### 3-plan/roadmap.md
- Stale reference: T00015 (archived)
- Missing from roadmap: T00021
All format requirements are in kb/references/:
| Document Type | Reference | Key Requirements |
|---|---|---|
| PRDs | prd-format.md | Header, Overview/Scope, prefix (feat-/comp-/infra-) |
| SOPs | sop-format.md | Header, Steps, verb-noun filename |
| Patterns | pattern-format.md | Status field (open/resolved), Problem section |
| Code Maps | codemap-format.md | Header, Last updated, Key Files |
| Tickets | ticket-formats.md | All 5 docs with required sections |
Read the relevant reference file to understand what to validate.
## Format Validation
| File | Issue |
|------|-------|
| 4-patterns/caching.md | Missing Status field |
| 2-sop/deploy.md | Filename should be verb-noun |
| tickets/T00022/1-definition.md | Missing Scope section |
Some issues can be auto-fixed:
Status: open to patternsThis is a Claude-interpreted skill (no CLI script). When invoked:
Usage:
/lint-kb # Claude performs validation, reports issues
/lint-kb fix patterns # Claude fixes specific category
# Tickets not in index
comm -23 <(ls -1 .pmc/docs/tickets/ | grep '^T' | sort) \
<(grep -oE 'T[0-9]+' .pmc/docs/tickets/index.md | sort)
# Patterns without Status
grep -L -i 'Status:' .pmc/docs/4-patterns/*.md
$ /lint-kb
Checking KB documentation...
## Scope
- Mode: recent (uncommitted + last 3 commits)
- Files to check: 8
## Ticket Completeness
| Ticket | Files | Status |
|--------|-------|--------|
| T00021 | 5/5 | COMPLETE |
| T00022 | 2/5 | Missing: 3-spec, 4-progress, 5-final |
## Index Integrity
tickets/index.md:
- Missing: T00022
3-plan/roadmap.md:
- OK
## Format Validation
4-patterns/new-pattern.md:
- Missing: Status field (add "Status: open" or "Status: resolved")
## Summary
- Errors: 2
- Warnings: 1
- Auto-fixable: 1 (run with --fix)
This skill should be used when the user asks to "create a hookify rule", "write a hook rule", "configure hookify", "add a hookify rule", or needs guidance on hookify rule syntax and patterns.
Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, or applications. Generates creative, polished code that avoids generic AI aesthetics.