Never Auto-Commit Rule

March 3, 2026 · View on GitHub

Critical Instruction

NEVER commit changes automatically after completing work.

What This Means

  • ❌ Do NOT commit after finishing a task
  • ❌ Do NOT commit after code changes
  • ❌ Do NOT commit after formatting or linting
  • ❌ Do NOT assume I want to commit

When to Commit

ONLY commit when explicitly instructed by me.

I will tell you to commit using phrases like:

  • "Commit the changes"
  • "Please commit"
  • "Now commit"
  • "Go ahead and commit"

What to Do Instead

After completing work:

  1. Summarize what was done
  2. Show any relevant output or results
  3. Stop and wait for further instructions
  4. Do NOT stage or commit files

Why This Rule Exists

I want full control over when commits happen. I may want to:

  • Review changes before committing
  • Make additional modifications
  • Commit related changes together
  • Skip committing for experimental work

Reminder

When in doubt, do NOT commit. Wait for explicit instruction.