regression-notes
Installation
SKILL.md
Regression notes
Version 0.6.0
Use python or py -3 when python3 is unavailable (stock Windows).
A lightweight port of the DeepSeek Harness Agent Note loop: a fix whose reason a later change could lose ships one note (the why) + one regression test (the lock) in the same change. The note records the decision; the test pins the behavior.
When to write a note
Notes are the exception, tests are the default. A note is read before every edit to the files it cites, so each one costs every future change a little attention; a tree with a note per bug turns a hot file's lookup into hundreds of entries nobody reads. Decide per fix:
| The fix… | Write |
|---|---|
| was introduced and fixed inside the same uncommitted change | nothing — it never reached anyone |
| is obvious from the code and its test | a regression test (prefer one more assertion in an existing test over a new file) and a clear commit message |
| has a reason that fits in one line at the fix | that test, plus a code comment at the fix — the comment sits exactly where the tempting edit happens |
| is a decision a later change could plausibly undo: the fixed code looks redundant or wrong, a tempting alternative was rejected, a trade-off was made (e.g. performance for correctness), or the fix spans files or a shared contract/format | a note bound to its regression test |