No Git Commands

Read-only git commands (status, diff, log, show, blame) are fine. Never run mutating ones (add, commit, push, reset, checkout, stash, etc.).

Source memory file: feedback_no_git_commands.md · Category: Feedback / working-preference This is a verbatim dump of Claude's persistent memory for the Octopus project. Rendered inside a code block so nothing is altered.

---
name: Read-only git only — never mutate
description: Read-only git commands (status, diff, log, show, blame) are fine. Never run mutating ones (add, commit, push, reset, checkout, stash, etc.).
type: feedback
originSessionId: eed33723-1d2b-417d-bbf4-ab9b2ef31e60
---
Read-only git commands are allowed: `git status`, `git diff`, `git log`, `git show`, `git blame`. Use them freely when useful for understanding state.

Never run mutating git commands: `git add`, `git commit`, `git push`, `git reset`, `git checkout` (when it changes files/branches), `git stash`, `git rebase`, `git merge`, `git pull`, `git tag`, etc. Do not offer to commit or push at the end of a task. **Do not ask about commit strategy either** — "single commit or separate?", "want me to split this into commits?", "should I squash?" are all forms of offering to commit. End at the summary; the user runs git themselves.

**Why:** The user drives all state-changing git operations themselves, but is fine with me inspecting repo state. Reinforced 2026-05-16 after I asked "commit Phase 1–3 as separate commits or one big commit?" at the end of a multi-phase docs task — that question is exactly the pattern this rule forbids.

**How to apply:** Override the default Claude Code behavior of offering to commit after completing work. When finishing a task, stop at a summary — do not suggest committing, do not ask about commit shape, do not preview a commit message. If you need to inspect history or changes, reach for read-only git commands directly.