kb-check
Skill15 starsChanged 25 days agoMITView on GitHub
Check the Pointframe knowledge base against the code and fix what it reports - paths, lessons, links across files, feature IDs, telemetry and smoke-test coverage, File map coverage, and the generated table of contents, Feature index, and Codex skill copies. Use after writing to the knowledge base; after renaming, moving, or adding files, telemetry events, or smoke tests; or when CI's "Knowledge base check" step fails.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- SterlingJF/knowledge-bustheir own version, first seen Sep 14, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- SterlingJF/knowledge-bus★ 4same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
The file
Files
/kb-check: check and fix
pwsh scripts/kb.ps1 check # refresh the generated parts, then check everything
pwsh scripts/kb.ps1 check -NoFix # check only, write nothing (what CI runs)check rewrites generated things, so never edit them by hand: the table of contents, Feature index, and decision index in docs/knowledge-base/knowledge-base.md, the Codex copies of the kb-* skills in .agents/skills/, and docs/knowledge-base/kb-baseline.json (it only lowers entries). Never edit the rendered skills or the vendored kit; change docs/knowledge-base/kb-slots.txt, then run pwsh scripts/kb.ps1 render (template changes come only with a kit release).
pwsh scripts/kb.ps1 selftest runs the tool against synthetic fixtures shipped with the workflow kit (scripts/verify.ps1 runs it first), and pwsh scripts/kb.ps1 stats prints bytes and estimated tokens per file, section, and task-suite task.
Fix every ERROR, then run check again until it prints 0 errors:
| Error says | Fix |
| path does not exist | The file moved or was renamed: update the path, or the section if behavior moved with it |
| path is gitignored | *.md is ignored by default: add a ! negation to .gitignore, or drop the path |
| lesson heading not found | Copy the exact ## heading from lessons.md |
| broken link | Point it at an existing heading; another file's section is other.md#anchor or ../other.md#anchor |
| tracked file matches no File map row | Add or widen a row in docs/knowledge-base/file-map.md, linking the narrowest section that owns the file |
| File map pattern matches no tracked file | The folder or file is gone: narrow or remove the pattern. A brand-new file must be tracked (git add -N) before it counts |
| File map row is redundant | Delete it, or give it a link the wider row does not have |
| links the container heading | A ## heading that only groups ### sections cannot be read; link one of its ### sections |
| section is N bytes, over 8192 / the core file is over 12288 | Split or compress it. Only violations already in docs/knowledge-base/kb-baseline.json are allowed, at their listed size or less; a section that grew past its entry fails until it shrinks again |
| baseline lists a section that is within the limit | Run check without -NoFix; it drops the entry |
| rule ID / unknown role / rule-section trigger / malformed rule marker | Fix the <!-- rule:W-NN roles=... --> or <!-- rule-section roles=... --> line in workflow.md: unique W-NN, roles from all, coordinator, executor, reviewer, and a trigger directly before a ## heading |
| lesson has N subsections / unknown subsection | A lesson needs exactly one ### Problem, ### What fixed it, and ### Takeaway; ### Root cause is optional |
| lesson is not linked from any section / only from sections nothing reaches | Add a - Lesson: line to the owning section, and make sure a File map row, a feature row, or a task reaches that section |
| task suite: task has recall below 1 | A routing change hid an expected section or lesson from kb read: fix the File map rows or links, or update docs/knowledge-base/kb-tasks.json when the expectation is really obsolete |
| telemetry event belongs to no feature | Add the event to the F-NN row that emits it |
| smoke test belongs to no feature | Add the test to the F-NN row it covers |
| feature ID is also used | IDs are never reused: give the new feature the next free F-NN |
| more than one Files. line | A block landed under the wrong heading: move it |
| is out of date | Run check without -NoFix |
A note is not an error, and a warn (a prose line over 600 characters, an area file over 40 KB, changelog phrasing in an area file) does not fail the check but should be fixed when you touch that text.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.