1.9 KiB
1.9 KiB
| description | alwaysApply |
|---|---|
| Never git commit without explicit user instruction; user reviews before any commit | true |
Commits and review (Neon Sprawl)
No commits without explicit instruction
- Do not run
git commit(or equivalent, e.g. committing via tools) unless the user explicitly asks—clear wording such as “commit this”, “make a commit”, or “commit with message …”. - Phrases like “implement X”, “begin work”, or “open a PR” are not implicit permission to commit.
- Default after edits: leave changes uncommitted (working tree or staged only if the user asked to stage). Summarize what changed and where so the user can review in the Git / diff UI, then wait for commit instructions.
Review before commit
- The user should review the diff before anything is committed. The agent’s job is to make the changes visible (uncommitted) and explain them; the user decides when to commit.
- If the user asks to commit, use a message that matches repo conventions; still follow git workflow (branch vs
main, doc-only vs code).
Pull request, commit messages, and push descriptions
- Do not add “Made-with: Cursor”, “Generated with Cursor”, tool co-author lines, or similar AI/IDE boilerplate to git commit messages (subject or body), PR descriptions, GitHub merge/squash commit bodies you draft, or other remote-facing narrative unless the user explicitly requests it.
- Keep PR text to scope, verification, and project-required contract snippets (e.g. from
docs/plans/). - After
git commit: rungit log -1 --format=%B(or check in the SCM UI). If the environment appended tool branding,git commit --amendto remove it beforegit push.
Scope
- Applies to all commits the agent might make, including documentation-only changes (e.g.
docs/plans/, README), not only application source.