groom-notes

To prune stale notes in a TOML file, the grooming workflow identifies references to removed files, conflicting statements, and duplicates, then presents a grouped summary awaiting your approval before applying changes. It cross-references mentions with git history to determine if notes should be retained or updated.

Yes, you can automatically suggest new documentation entries by scanning git history and recent changes. The workflow ensures no duplicates are created and aligns new suggestions with documented lessons, preserving general lessons even if the underlying code moved.

Yes, the notes grooming workflow requires explicit user approval before modifying notes.toml. It groups proposed changes such as pruning, duplicate removal, and adding new notes, ensuring safe changes by waiting for your confirmation before execution.

The best way to remove duplicate and conflicting entries from project notes is using an automated grooming workflow. It identifies stale mentions, conflicts, and duplicates in your notes.toml file, preserving headers and general lessons while presenting a summary for your approval.

Yes, the notes grooming process will preserve your existing headers and general lessons. Even if code is moved or removed, the workflow retains general lessons and maintains headers, only pruning stale entries or suggesting updates after receiving explicit approval.