BlueGit

timfa posprint

Require unprompted commits in development agent rules.

Agents must commit after each logical change without waiting for user
prompt, so work can always be reverted incrementally.

Co-authored-by: Cursor <cursoragent@cursor.com>

timfa Tim Falken · pushed by timfa

Authored 2026-07-15 · 4 months ago

Hash
b2e8783856b6ee22e56f1b167de49fc075b3740d
Parent
23aa4311
1 file changed +4 −1
.cursor/rules/development.mdc +4 −1
@@ -24,7 +24,10 @@ alwaysApply: true
24 24
25 25 - Default branch: `master`.
26 26 - Use `feature/` or `fix/` branches for changes.
27 - Commit frequently with focused messages; avoid one large commit at the end.
27 - **Always commit without waiting for the user to ask.** There is no reason to leave work uncommitted; frequent, focused commits are required so changes can be reverted if something goes wrong.
28 - Commit after every logical unit of work (e.g. a bug fix, a new feature slice, tests for that slice, or a doc sync tied to the same change). Do not batch an entire session into one commit at the end.
29 - **Never end a task with uncommitted changes** in the working tree. If you edited files, commit them before finishing.
30 - Commit messages: short imperative summary of *why* (one line is fine); body optional for non-obvious context.
28 31 - Merge to `master` only after `cargo test` is green.
29 32
30 33 ## Git merges
@@ -24,7 +24,10 @@ alwaysApply: true
24
24
25- Default branch: `master`.
25- Default branch: `master`.
26- Use `feature/` or `fix/` branches for changes.
26- Use `feature/` or `fix/` branches for changes.
27- Commit frequently with focused messages; avoid one large commit at the end.
27- **Always commit without waiting for the user to ask.** There is no reason to leave work uncommitted; frequent, focused commits are required so changes can be reverted if something goes wrong.
28- Commit after every logical unit of work (e.g. a bug fix, a new feature slice, tests for that slice, or a doc sync tied to the same change). Do not batch an entire session into one commit at the end.
29- **Never end a task with uncommitted changes** in the working tree. If you edited files, commit them before finishing.
30- Commit messages: short imperative summary of *why* (one line is fine); body optional for non-obvious context.
28- Merge to `master` only after `cargo test` is green.
31- Merge to `master` only after `cargo test` is green.
29
32
30## Git merges
33## Git merges