neat-freak
Knowledge and governance closeout: reconcile project docs, rule files (CLAUDE.md/AGENTS.md), authorized agent memory, and workspace residue with what the code and runtime actually do, so the next session or the next person starts from one current answer. Trigger when the user names "neat-freak", "洁癖", or "/neat" — and also on clear knowledge-closeout intent without the name: syncing or tidying project docs/rules/memory after development ("把文档和记忆整理一下", "收尾时把文档同步掉", "docs 和代码对不上了"), stale or conflicting CLAUDE.md/memory, a clean handoff to a teammate or a fresh session, or auditing whether works
npx skills add KKKKhazix/khazix-skills --skill neat-freak --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# 洁癖 — Knowledge and Governance Closeout 你是知识库编辑、规范审计员和收尾者。目标不是「多写一点」，而是让代码、真实运行态、项目文档、Agent 规则、获准维护的记忆和工作区状态彼此一致，让下一次会话或第一次接手的人能找到唯一现役答案。 ## 完成合同 一次洁癖收尾只有在相关事实面都得到明确状态后才算完成： | 事实面 | 要回答的问题 | 常见证据 | |---|---|---| | 代码 | 现在真正实现了什么？ | 当前分支、schema、配置、测试 | | 运行态 | 用户实际得到什么？ | deploy marker、服务、真实页面/API、控制台 | | 文档 | 人和下游看到的是不是现役答案？ | README、架构、接入、运维文档 | | 规则 | Agent 收到的约束是否同源、可执行、无死引用？ | 层级 CLAUDE.md/AGENTS.md、override、hooks | | 记忆 | 快照是否仍准确且允许修改？ | 平台记忆入口、索引、生成来源 | | 工作区 | 是否仍有未集成或未审计的残留？ | 会话残留文件、worktree、分支、临时库 | 每一面标成 `verified-current`、`changed-and-verified`、`pending`、`out-of-scope` 或 `not-applicable`。小项目不必硬凑六个面：没有部署就没有运行态面，没有记忆系统就没有记忆面——如实标 `not-applicable`，不要编造证据。不要把 `git status` 干净、PR 已合并或测试通过单独当成「全部同步」。发布状态必须区分 draft、PR、merged、deployed、live verified、knowledge closed 和 cleaned。 ## 权限和范围先于洁癖 当前系统、用户和项目规则始终高于本 skill。洁癖扩大检查深度，不扩大操作权限。 先判断请求属于哪一档： 1. **文档同步**：当前项目的代码/文档/规则一致性；记忆默认只读，除非用户或项目收尾规则明确授权写入。 2. **知识收尾**：文档、规则、获准维护的记忆和会话复盘。 3. **发布收尾**：在知识收尾之外核对本地、远端、生产和 live surface；知识凭证完成后才能清场。 4. **工作区审计**：只有用户明确说「整个 workspace / 全部项目 / 审全部」时，才逐项目扩大内容审计。 清场会删除分支、worktree、临时库或中间产物，属于不可在交付汇报前自动吞掉的破坏性收尾。默认顺序是：先完成知识收尾和只读清场预览，向用户完整汇报并保留复核现场；只有用户看完汇报后明确确认可以清场，才执行删除并补充汇报清场结果。用户在最初任务里说「做完后清理」不替代这次
- 完成合同
- 权限和范围先于洁癖
- 先选路径：轻量还是完整
- 轻量路径（五步）
- 完整路径
- 知识放在哪里
- 执行流程（完整路径）
- 0. 发现平台、规则和体量
- 1. 建立现役事实矩阵
- 2. 审计规则和实践
- 3. 路由受影响知识面
- 4. 先减后加地修改
- 5. 谨慎处理记忆
- 6. 验证并完成发布闭环
What does the neat-freak skill do?
Knowledge and governance closeout: reconcile project docs, rule files (CLAUDE.md/AGENTS.md), authorized agent memory, and workspace residue with what the code and runtime actually do, so the next session or the next person starts from one current answer. Trigger when the user names "neat-freak", "洁癖", or "/neat" — and also on clear knowledge-closeout intent without the name: syncing or tidying project docs/rules/memory after development ("把文档和记忆整理一下", "收尾时把文档同步掉", "docs 和代码对不上了"), stale or conflicting CLAUDE.md/memory, a clean handoff to a teammate or a fresh session, or auditing whether works
How do I install it?
Run `npx skills add KKKKhazix/khazix-skills --skill neat-freak --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From KKKKhazix/khazix-skills, a repository with 19,062 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.