Nobody writes the post-mortem, so my bug fixes write their own

说明与用途

开发者很少记录事后分析，导致错误重复。Bug Diary 自动记录事后分析，比较新更改与过去经验，并在提交前发出警告，降低错误重复率。

问题

Developers rarely document post‑mortems, so recurring bugs are not learned from past fixes.

结果

Bug Diary reduced repeated bugs by warning on vulnerable code in 33 out of 92 later bugs and only warned on one of 21 ordinary commits.

工作流

• 1. Commit a fix with a message starting with "fix".
• 2. Git hook triggers Bug Diary after the commit.
• 3. Bug Diary reads the diff, test, commit message, and issue.
• 4. Gemma 4 writes a post‑mortem card (symptom, root cause, pattern, guard, lesson).
• 5. EmbeddingGemma finds closest lessons in the diary.
• 6. Before a new commit, Bug Diary checks the change against lessons and alerts if a pattern repeats.
• 7. If a warning appears, the developer reviews the alert and writes a test or guard.
• 8. The diary updates with the new lesson for future checks.

证据

After a fix, it reads the diff, the new test, the commit message, and the issue if there is one, and Gemma 4 writes the post‑mortem nobody writes: symptom, root cause, pattern, the guard the fix added, and one lesson for next time.

来源

Before a commit, it describes what your change does, finds the closest lessons in the diary, and checks whether your change repeats one of them.

来源

Bug Diary warned on the vulnerable version of 33 bugs and on the fixed version of 14: for 24 bugs it warned on the vulnerable version only, and for 5 the other way round.

来源