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 workspace rules are actually followed. Do not trigger for pure coding/refactoring/debugging tasks, tidying data or prose (JSON, 周报, changelog announcements), or a bare "整理" with no project-knowledge context.
Ask your Agent
Use this Skill: https://skilld.dev/gh/kkkkhazix/khazix-skills/neat-freak
This session only. Nothing lands on disk.
≈120 tokens on demand. Your agent reads this file only when SKILL.md points to it.
团队任务管理工具，个人使用。
npm install
npm run dev # Express 起在 :4000GET /api/tasks — 任务列表POST /api/tasks — 创建任务PATCH /api/tasks/:id — 更新任务DELETE /api/tasks/:id — 删除任务部署到 Vercel（vercel --prod）。
Source: SKILL.md on GitHub
The skill 'neat-freak' is a project governance and documentation reconciliation tool designed to synchronize project documentation, agent rules, and memory with the actual state of the code. It includes strong safety guardrails, such as requiring explicit user confirmation for any destructive operations (like cleaning up temporary files or branches) and explicitly forbidding the exfiltration or storage of credentials discovered during audits. The skill uses a dedicated read-only Bash script to inventory project artifacts, and no malicious patterns or vulnerabilities were detected.
No alerts
Risk: LOW · No issues
Signed by skilld at 2b4a645. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.
Last checked against GitHub 7 hours ago.
{
"version": "3.0.0",
"category": "knowledge-governance"
}