neat-freak
Knowledge and governance closeout: reconcile project docs, rule files
by kkkkhazixFree
Description
Neat Freak is an agent skill for closing out a piece of work by tidying its knowledge. It acts as a knowledge base editor and governance auditor, with the goal that the code, the running system, the project documents, the agent rule files, any agent memory you have authorized and the workspace all agree, so that the next session or the next person can find one current answer. It checks six fact surfaces. For the code, it asks what is actually implemented, using the branch, schema, configuration and tests. For the runtime, it asks what users actually get, using deploy markers, services and live pages. Documentation is checked for whether readers see the current answer, rule files such as CLAUDE.md and AGENTS.md are checked for whether agents receive consistent, executable constraints, agent memory is checked for accuracy, and the workspace is checked for leftover files, worktrees and branches. Each surface is marked verified-current, changed-and-verified, pending, out-of-scope or not-applicable, and the skill says not to treat a clean git status or passing tests as proof that everything is in sync. It also separates release states such as draft, pull request, merged, deployed, live verified, knowledge closed and cleaned. The skill is published under the khazix-skills repository on skills.sh, which has about 21.4K stars, and the listing shows Gen Agent Trust Hub, Socket and Snyk all passing.…
Highlights
- Reconciles code, runtime, docs, rules, memory and workspace
- Five-status verdict for each fact surface
- Separates release states from merged to cleaned
- Does not treat a clean git status as proof
- Works with CLAUDE.md and AGENTS.md rule files
Ratings & Reviews
No ratings yet
Be the first to rate neat-freak.
People also visit
neat-freak FAQ
What does the skill do?
It closes out a piece of work by checking that code, running system, docs, agent rules, authorized memory and workspace give the same current answer.
What counts as done?
Each fact surface must have a clear status: verified-current, changed-and-verified, pending, out-of-scope or not-applicable.
Does passing tests settle it?
No. The skill says a clean git status, a merged pull request or passing tests should not be treated alone as everything being in sync.
Which files does it check?
Project docs such as the README and architecture notes, the rule files CLAUDE.md and AGENTS.md, and authorized agent memory.
How do I install it?
Run npx skills add https://github.com/kkkkhazix/khazix-skills --skill neat-freak.
What are the best neat-freak alternatives?
Popular alternatives to neat-freak include living-docs-governance, compound-docs and google-cloud-recipe-foundation-builder. See all neat-freak alternatives