1. Habit
  2. Skills
  3. Neat Freak skill
kkkkhazix · 3K installs

Neat Freak skill
Runs by itself, after each merged change.

Your docs stay true.

Install the Neat Freak skill and make it a habit: follow https://gethabit.dev/skills/kkkkhazix/neat-freak.md

  1. 1Copy
  2. 2Paste into Claude Code, Codex or Cursor
  3. 3It runs by itself

3K installs22K starsMIT licenceSource on GitHub ↗

Neat Freak

by kkkkhazix · 3K installs

The skill

Cleans up docs and rules so they match your code.

Only when you ask.

Time saved

Your docs stay true. The next person starts clean and loses less time.

↻ Runs by itselfafter each merged change

How the habit works.
You don't have to.

Three questionsWhen does it start? How does it check its work? What does it remember?

01

It starts by itself

change merged. Runs in Claude Code routine.

  • ↻ change merged
  • pull_request.closed && merged

02

It checks its work

fact surfaces + your confirmation. If a check fails, it tells you.

  • ✓every fact surface has a status such as verified-current, pending or not-applicable
  • ✓no file was deleted before your confirmation
  • ✓the project's existing lint, test or build gates pass

03

It remembers

project rules file. The next run reads it first: the project's one-line purpose, run commands, stack, conventions and current status.

CLAUDE.md

One run, step by step.
Then it stops.

Stop ruleStops after one closeout report per merge; cleanup runs only in a second step after your yes.

  1. 01

    Pick the path

    Use the light path for small solo projects and the full path when release flows or multiple platforms are involved.

  2. 02

    Inventory

    Run bash scripts/audit-inventory.sh on the project root, or do the same checks by hand.

  3. 03

    Align facts

    Compare docs with current code for commands, ports, dependencies and features, fixing stale text in place.

  4. 04

    Fix the rules file

    Create a short rules file if none exists, or fix only contradictions in the existing one.

  5. 05

    List leftovers

    List finished plan files, debug scripts and old copies as delete candidates with reasons.

  6. 06

    Report and wait

    Report impact, changes, candidates and pending items, then clean up only after you confirm.

What it may do.
Nothing more.

Safe by defaultIt writes only in its own folder and asks you before anything goes out.

Is it for you?
Use it when it fits.

Quick checkRead both lists. If the left one sounds like you, the Neat Freak skill helps.

Use it when

  • ✓ Docs no longer match the code
  • ✓ You hand a project to someone else
  • ✓ Your CLAUDE.md is stale

Skip it when

  • – You are in the middle of coding
  • – You want to tidy data or prose files

Questions

Neat Freak skill, answered.

Will it delete old files on its own?

No. Deletions are listed as candidates and wait for your explicit confirmation after the report.

Does a clean git status mean everything is in sync?

No. The skill says to check code, runtime, docs, rules, memory and workspace separately.

Does it edit agent memory?

Only when you or the project rules allow it; by default memory is read-only.

How do I install the Neat Freak skill?

Copy the prompt at the top into your agent. It installs the skill from kkkkhazix/khazix-skills and sets up the habit. Or run npx skills add kkkkhazix/khazix-skills --skill neat-freak.

Is the Neat Freak skill free?

Yes. It is published under MIT. Habit is free too.

Neat Freak. Now as a habit.

Install the Neat Freak skill and make it a habit: follow https://gethabit.dev/skills/kkkkhazix/neat-freak.md

  • Free
  • No account
  • Undo in one line

All kkkkhazix skills →More docs skills →

Works in

  • Claude Code
  • Codex
  • Cursor
  • ChatGPT
  • Claude app

Made by kkkkhazix, published under MIT. Habit links to the original and never changes it. Is this your skill?

Copying didn't work here. Select the line and copy it by hand.