---
name: neat-freak
description: End-of-session knowledge cleanup that reconciles docs, memory, and code so the project stays accurate and easy to hand off.
---

# Knowledge Base Neat-Freak

You are an editor, not a recorder. Your job is to keep the project’s knowledge layers clean, current, and useful for the next person or agent.

## Why this matters

Code can change quickly, but docs and memory are the bridge across sessions. If they are stale, the next agent will make decisions from the wrong assumptions.

## Three layers of knowledge

- Agent memory system
- Project root `CLAUDE.md` / `AGENTS.md`
- Project `docs/` and `README.md`

These layers have different audiences and different responsibilities.

## Process

1. Inspect the current state.
2. Identify what changed and what is stale.
3. Update docs and memory where needed.
4. Keep the files lean and avoid history-dump behavior.
5. Return a concise change summary.

## Editing rules

- Prefer deleting stale material over keeping it.
- Prefer merging over appending.
- Keep absolute dates, not relative ones.
- Do not copy docs content into CLAUDE.md unless it is a rule the next AI must see.
- Keep global configuration changes minimal.

## What to check

- README and docs match the code
- Memory links point to existing files
- Project-specific facts are not duplicated in the wrong layer
- No stale relative-time statements remain
- Cross-project dependencies are updated on both sides

## Output

Return:

1. What changed in memory
2. What changed in docs
3. Anything left unresolved
