One-click install
npx skills add https://github.com/JerryLinyx/muce --skill neat-freak-jerrylinyx
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: neat-freak
Source: https://github.com/JerryLinyx/muce/tree/main/.claude/skills/neat-freak
Command: npx skills add https://github.com/JerryLinyx/muce --skill neat-freak-jerrylinyx

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill prevents project knowledge from rotting by reconciling end-of-session documentation and agent memory with the current codebase state, so future work starts from accurate facts.

Core Features & Use Cases

  • Global doc & memory reconciliation: Audits and synchronizes cross-session knowledge across project root docs (CLAUDE.md/AGENTS.md or equivalents), docs/ and README, and any supported agent memory layer.
  • Anti-entropy governance: Detects and removes outdated, conflicting, or redundant information; merges duplicates; and prevents history-like narratives from polluting rule/memory layers.
  • Fresh onboarding clarity: Ensures external readers (and downstream agents) have correct, concise integration and operational guidance aligned with the latest implementation.

Common use case: after finishing a feature or discovering drift (stale/conflicting docs or memory), run a cleanup pass so the next agent can safely follow the “rules and routes” and the “external docs” without guessing.

Quick Start

Use the neat-freak skill when your team says “sync up” (or you observe stale or conflicting docs) to reconcile README, CLAUDE.md/AGENTS.md, docs/, and supported memory against the current project state.

Frequently Asked Questions about neat-freak

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

FAQPage Schema
How do I keep project documentation and agent memory in sync with the codebase?

To keep project documentation and agent memory in sync with the codebase, run a structured reconciliation audit at the end of your session. This process detects stale docs and conflicting memories, updating them against the current implementation to prevent knowledge rot.

What is agent memory pollution and how do I prevent it during handoff?

Agent memory pollution occurs when history-like narratives or outdated entries clutter rule layers like CLAUDE.md. Prevent it during handoff by enforcing anti-pollution rules that keep these files as boundaries, removing redundant information and merging duplicates.

How do I detect stale docs and conflicting routes before onboarding a new agent?

Detect stale docs and conflicting routes by executing a completeness validation check across all relevant markdown files. This audit reconciles project root docs, README, and memory layers with the current codebase state to ensure fresh onboarding clarity.

Can I use this documentation sync approach for multi-agent continuity?

Yes, you can use this documentation sync approach for multi-agent continuity. By reconciling end-of-session knowledge and removing outdated entries, it ensures downstream agents receive correct, concise integration and operational guidance aligned with the latest implementation.

What is the best way to clean up outdated CLAUDE.md and AGENTS.md files?

The best way to clean up outdated CLAUDE.md and AGENTS.md files is to apply anti-entropy governance. This removes outdated or conflicting information while enforcing that these files act as strict boundaries rather than historical narratives, ensuring accurate cross-session knowledge.