update-notes

To capture engineering insights, you can use a zettelkasten approach that stores non-obvious codebase findings in a project-scoped .notes/ directory. This preserves institutional memory by automatically indexing and categorizing durable engineering truths across the project lifecycle.

The best way to maintain codebase notes without duplicates is using an idempotent knowledge-management process. By enforcing stable slugs for each note, the system ensures safe repeated runs that update existing entries rather than generating duplicate files.

Automated indexing for a project-scoped zettelkasten works by regenerating an INDEX.md file after each update. This reflects new or modified notes across the project lifetime, ensuring the knowledge base remains navigable and up-to-date without manual curation.

Yes, you can categorize engineering notes and cross-link related codebase findings. Notes support cross-linking via related fields and can be organized into predefined seeds like api-surface, architecture, gotchas, or conventions to structure your knowledge effectively.

Only non-obvious engineering findings should be stored in a project knowledge base. The system explicitly rejects trivial observations, focusing instead on durable truths, architectural decisions, and hidden gotchas that preserve genuine institutional memory.

No, update-notes does not require external dependencies to manage codebase notes. It operates independently to write findings into the .notes/ directory and regenerate the INDEX.md file, requiring no prior environment setup or package installations.