A Claude Code command that sifts your notes into a knowledge base every night

Today's file is a Claude Code command for what you learn while working: where a service lives, the command that really builds the report, the trap you fell into on Tuesday. It goes into a note, newer notes bury it, and three months later a new session falls into the same trap. Prosev runs at night, reads the notes changed in the last day and moves what will still matter into a knowledge base.

How it works

The filter is one question: will this entry save a new session, three months from now, doing a different task in the same place, at least one step. The progress of a task, one-off measurements and dates, what one query to the code would show, secrets and anything personal stay out. Of a password it keeps only the name of the environment variable that holds it.

Before writing, it searches $HOME/knowledge by the distinctive words of each entry (a path, a command, a service name) and reads the whole section it finds. Already there: skipped. Written differently: fixed in place, with the date it was seen. Missing: added to the file that fits the topic, and a new file only when none does. Then it reads back every place it changed and puts the file back if something does not match.

It deletes and shortens nothing, neither notes nor entries. The reply is one line, "All good, all done.", also on a night with nothing to add. Errors, if there are any, come instead, one per line.

What to change

The folders are $HOME/notes and $HOME/knowledge. If your notes live elsewhere, change the paths in the file and in the run command. The run uses --permission-mode acceptEdits: edits inside the folder it starts in and the two --add-dir folders go through without asking, so deleting nothing is a rule in its prompt, not a lock. Start it from $HOME/knowledge rather than your home folder, where cron starts it, and keep that folder in git.

Install

One file goes into ~/.claude/commands/. The note below then asks Claude for three things: the two folders, a short note at the end of every work task, and a daily run at 3:00 with claude -p '/prosev'. The computer stays on and awake at night. The check puts one line into a note, runs /prosev and expects that line in the knowledge base once, still once after a second run.