neat-freak

Reconciles project documentation and agent memory against code and audits workspace rule compliance.

Updated Jan 10, 2026
One-click install
npx skills add https://github.com/Rabbit-Ivan/Ivan-skills --skill neat-freak-rabbit-ivan
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: neat-freak
Source: https://github.com/Rabbit-Ivan/Ivan-skills/tree/main/skills/neat-freak
Command: npx skills add https://github.com/Rabbit-Ivan/Ivan-skills --skill neat-freak-rabbit-ivan

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? After a development session, project docs, CLAUDE.md/AGENTS.md files, and agent memory drift out of sync with the actual code, and workspace conventions quietly stop being followed. This Skill performs an end-of-session cleanup that reconciles all knowledge layers against the code and audits whether the workspace's own rules (naming, required files, symlink integrity, dead references) are being enforced. ## Core Features & Use Cases - Three-layer knowledge reconciliation: Aligns agent memory, project-root CLAUDE.md/AGENTS.md, and docs/ with the current code, including cross-project downstream documentation. - Anti-bloat governance: Enforces size budgets (e.g., MEMORY.md under 25KB/200 lines), promotes stable memories into docs via a graduation mechanism, and strips historical narrative out of rule files. - Rule execution audit: Extracts mechanically verifiable conventions from hierarchical rule files, checks practice against them, auto-fixes safe violations, and escalates destructive ones for human decision. - Use Case: After shipping a new API with new environment variables, say "sync up" and the Skill updates the route list in CLAUDE.md, the integration guide, architecture docs, and runbook, prunes stale memories, and reports any naming or symlink violations it found. ## Quick Start Tell the agent "sync up the docs and memory after this session" and it will inventory, reconcile, and audit the project knowledge base.

Frequently Asked Questions about neat-freak

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I keep CLAUDE.md and docs in sync with my code?▼

Trigger this Skill at the end of a development session with phrases like "sync up" or "tidy up docs". It inventories every markdown file, maps code changes to affected documents via a change-impact matrix, and edits docs, CLAUDE.md, and memory in place.

How do I prevent agent memory from growing too large?▼

The Skill enforces a hard budget of 200 lines or 25KB on the MEMORY.md index, beyond which Claude Code silently stops loading entries. It shrinks memory through a graduation mechanism that promotes stable knowledge into docs/ and deletes or collapses the original memory files.

Does this work with OpenAI Codex and OpenCode, not just Claude Code?▼

Yes, it is cross-platform and supports Claude Code, OpenAI Codex, OpenCode, and OpenClaw. A reference file maps each platform's memory and config paths, such as ~/.codex/AGENTS.md for Codex and ~/.config/opencode/ for OpenCode.

What kinds of rule violations does the audit fix automatically?▼

It directly fixes safe, reversible issues like a missing AGENTS.md symlink to CLAUDE.md, absent .env entries in .gitignore, and dead references to confirmed-deleted projects. Destructive actions like directory renames or merging divergent files are escalated for human approval.

When should I not put information into CLAUDE.md?▼

Do not add historical narratives, detailed mechanism explanations, or one-off incident retrospectives to CLAUDE.md; those belong in git history, changelogs, or docs/. The test is whether an AI writing code next session would make a mistake without seeing that line.