| ... | ... | @@ -114,7 +114,6 @@ An empty database is a bad test. Seed your worktree's `.t3` with a copy of real |
| 114 | 114 | - Never make a PR unless the developer explicitly asks you to do so. |
| 115 | 115 | - Conventional commit titles, plain language: `fix(web): new threads no longer spike CPU`. |
| 116 | 116 | - Body: the problem in a sentence or two, then how you fixed it. End with the model and harness that did the work. |
| 117 | | - **Rebase onto latest main before opening.** Stale branches conflict and burn a review round. |
| 118 | 117 | - UI changes need before/after images. Motion or timing needs a short video. |
| 119 | 118 | - One concern per PR. If the description says "also", split it. |
| 120 | 119 | - When babysitting: poll checks and comments newer than the last push, verify each bot finding against the source, fix real ones, dismiss false positives with a written reason. Stay quiet when nothing is new. Stop when the bots are green on the latest commit. |
Julius Marminge <julius0216@outlook.com> 2026-08-13 17:04:42+02:00
GitHub <noreply@github.com> 2026-08-13 15:04:42+00:00