Suggest Commit

Git Command Safety

NEVER use cd <path> && git compound commands — they trigger security approval prompts. Run git commands directly (the working directory is already the target repo), or use git -C <path> if you need to target a different directory.

Critical Rules

ALWAYS:

• Run the git commands below EVERY time - never assume or remember previous state
• Base suggestions ONLY on the actual git diff --cached output from THIS invocation
• Only consider staged changes (--cached) — unstaged changes, untracked files, and working tree modifications are irrelevant

NEVER:

• Use conversation history, memory, or previously seen file changes as input for the suggestion
• Reference or incorporate any code changes you may have seen, made, or discussed earlier in this conversation — they are not the source of truth; only the staged diff output is
• Include the "Generated with Claude Code" footer, "Co-Authored-By: Claude" line, or any other Claude Code attribution text
• Add any text outside the code fence — no preamble, no trailing notes, change analysis, or commentary
• Mention plans, phases, steps, tasks or items, or any reference number — issue, ticket, bug, work item or PR numbers (#123, AB#4567, JIRA-89), plan item numbers ("Phase 2, item 3") or similar IDs — not even when the branch name, the conversation or a plan file contains one. Describe what the code change does, nothing else