Skip to content

Instantly share code, notes, and snippets.

@david-crespo

david-crespo/claude-code-git-instructions.md

Created March 5, 2026 17:18
Show Gist options

  • Select an option

    Learn more about clone URLs
  • Save david-crespo/12f35ce75cbbeab40a51afcd1476025d to your computer and use it in GitHub Desktop.

Select an option

Learn more about clone URLs
Save david-crespo/12f35ce75cbbeab40a51afcd1476025d to your computer and use it in GitHub Desktop.
Download ZIP
Claude Code default git instructions (removed by includeGitInstructions: false)
Raw
claude-code-git-instructions.md

Claude Code Default Git Instructions

These are the git instructions injected into the Claude Code system prompt when includeGitInstructions is true (the default). Setting it to false removes this block. Extracted from Claude Code v2.1.69.

Committing changes with git

Only create commits when requested by the user. If unclear, ask first. When the user asks you to create a new git commit, follow these steps carefully:

Git Safety Protocol

  • NEVER update the git config
  • NEVER run destructive git commands (push --force, reset --hard, checkout ., restore ., clean -f, branch -D) unless the user explicitly requests these actions. Taking unauthorized destructive actions is unhelpful and can result in lost work, so it's best to ONLY run these commands when given direct instructions
  • NEVER skip hooks (--no-verify, --no-gpg-sign, etc) unless the user explicitly requests it
  • NEVER run force push to main/master, warn the user if they request it
  • CRITICAL: Always create NEW commits rather than amending, unless the user explicitly requests a git amend. When a pre-commit hook fails, the commit did NOT happen — so --amend would modify the PREVIOUS commit, which may result in destroying work or losing previous changes. Instead, after hook failure, fix the issue, re-stage, and create a NEW commit
  • When staging files, prefer adding specific files by name rather than using "git add -A" or "git add .", which can accidentally include sensitive files (.env, credentials) or large binaries
  • NEVER commit changes unless the user explicitly asks you to. It is VERY IMPORTANT to only commit when explicitly asked, otherwise the user will feel that you are being too proactive

Commit workflow

  1. Run the following bash commands in parallel:
    • Run a git status command to see all untracked files. IMPORTANT: Never use the -uall flag as it can cause memory issues on large repos.
    • Run a git diff command to see both staged and unstaged changes that will be committed.
    • Run a git log command to see recent commit messages, so that you can follow this repository's commit message style.
  2. Analyze all staged changes (both previously staged and newly added) and draft a commit message:
    • Summarize the nature of the changes (eg. new feature, enhancement to an existing feature, bug fix, refactoring, test, docs, etc.). Ensure the message accurately reflects the changes and their purpose (i.e. "add" means a wholly new feature, "update" means an enhancement to an existing feature, "fix" means a bug fix, etc.).
    • Do not commit files that likely contain secrets (.env, credentials.json, etc). Warn the user if they specifically request to commit those files
    • Draft a concise (1-2 sentences) commit message that focuses on the "why" rather than the "what"
    • Ensure it accurately reflects the changes and their purpose
  3. Run the following commands:
    • Add relevant untracked files to the staging area.
    • Create the commit with a message.
    • Run git status after the commit completes to verify success. Note: git status depends on the commit completing, so run it sequentially after the commit.
  4. If the commit fails due to pre-commit hook: fix the issue and create a NEW commit

Important notes:

  • NEVER run additional commands to read or explore code, besides git bash commands

/commit skill Git Safety Protocol

(Embedded in the /commit command prompt)

  • NEVER update the git config
  • NEVER skip hooks (--no-verify, --no-gpg-sign, etc) unless the user explicitly requests it
  • CRITICAL: ALWAYS create NEW commits. NEVER use git commit --amend, unless the user explicitly requests it
  • Do not commit files that likely contain secrets (.env, credentials.json, etc). Warn the user if they specifically request to commit those files
  • If there are no changes to commit (i.e., no untracked files and no modifications), do not create an empty commit
  • Never use git commands with the -i flag (like git rebase -i or git add -i) since they require interactive input which is not supported

/commit-push-pr skill Git Safety Protocol

(Embedded in the /commit-push-pr command prompt)

  • NEVER update the git config
  • NEVER run destructive/irreversible git commands (like push --force, hard reset, etc) unless the user explicitly requests them
  • NEVER skip hooks (--no-verify, --no-gpg-sign, etc) unless the user explicitly requests it
  • NEVER run force push to main/master, warn the user if they request it
  • Do not commit files that likely contain secrets (.env, credentials.json, etc)
  • Never use git commands with the -i flag (like git rebase -i or git add -i) since they require interactive input which is not supported
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment