tool-description-bash-git-commit-and-pr-creation-instructions

name	Tool Description: Bash (Git commit and PR creation instructions)
description	Instructions for creating git commits and GitHub pull requests
ccVersion	2.1.162
variables	["BASH_TOOL_NAME","COMMIT_CO_AUTHORED_BY_CLAUDE_CODE","GET_TODO_TOOL_FN","TASK_TOOL_NAME","EMPTY_STRING","PR_INSTRUCTIONS_PREFIX","PR_GENERATED_WITH_CLAUDE_CODE","PR_COMMON_OPERATIONS_NOTE"]
allowed-tools	Read Write Edit Bash
license	BSD-3-Clause license
metadata	{"skill-author":"Lord1Egypt"}

${""}# 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:

You can call multiple tools in a single response. When multiple independent pieces of information are requested and all commands are likely to succeed, run multiple tool calls in parallel for optimal performance. The numbered steps below indicate which commands should be batched in parallel.

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

1. Run the following bash commands in parallel, each using the ${BASH_TOOL_NAME} tool:

• 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 in parallel:
   • Add relevant untracked files to the staging area.
   • Create the commit with a message${COMMIT_CO_AUTHORED_BY_CLAUDE_CODE? ending with: ${COMMIT_CO_AUTHORED_BY_CLAUDE_CODE}:"."}
   • 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
• NEVER use the ${GET_TODO_TOOL_FN} or ${TASK_TOOL_NAME} tools
• DO NOT push to the remote repository unless the user explicitly asks you to do so
• IMPORTANT: 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.
• IMPORTANT: Do not use --no-edit with git rebase commands, as the --no-edit flag is not a valid option for git rebase.
• If there are no changes to commit (i.e., no untracked files and no modifications), do not create an empty commit
• In order to ensure good formatting, ALWAYS pass the commit message via a HEREDOC, a la this example:

git commit -m "$(cat <<'EOF' Commit message here.${COMMIT_CO_AUTHORED_BY_CLAUDE_CODE?`

${COMMIT_CO_AUTHORED_BY_CLAUDE_CODE}`:""} EOF )"

${EMPTY_STRING?`${EMPTY_STRING}

`:""}# Creating pull requests Use the gh command via the Bash tool for ALL GitHub-related tasks including working with issues, pull requests, checks, and releases. If given a Github URL use the gh command to get the information needed.

${PR_INSTRUCTIONS_PREFIX}IMPORTANT: When the user asks you to create a pull request, follow these steps carefully:

1. Run the following bash commands in parallel using the ${BASH_TOOL_NAME} tool, in order to understand the current state of the branch since it diverged from the main branch:
   • Run a git status command to see all untracked files (never use -uall flag)
   • Run a git diff command to see both staged and unstaged changes that will be committed
   • Check if the current branch tracks a remote branch and is up to date with the remote, so you know if you need to push to the remote
   • Run a git log command and git diff [base-branch]...HEAD to understand the full commit history for the current branch (from the time it diverged from the base branch)
2. Analyze all changes that will be included in the pull request, making sure to look at all relevant commits (NOT just the latest commit, but ALL commits that will be included in the pull request!!!), and draft a pull request title and summary:
   • Keep the PR title short (under 70 characters)
   • Use the description/body for details, not the title
3. Run the following commands in parallel:
   • Create new branch if needed
   • Push to remote with -u flag if needed
   • Create PR using gh pr create with the format below. Use a HEREDOC to pass the body to ensure correct formatting.

gh pr create --title "the pr title" --body "$(cat <<'EOF'

Summary

<1-3 bullet points>

Test plan

[Bulleted markdown checklist of TODOs for testing the pull request...]${PR_GENERATED_WITH_CLAUDE_CODE?`

${PR_GENERATED_WITH_CLAUDE_CODE}`:""} EOF )"

Important:

• DO NOT use the ${GET_TODO_TOOL_FN} or ${TASK_TOOL_NAME} tools
• Return the PR URL when you're done, so the user can see it

Other common operations

• View comments on a Github PR: gh api repos/foo/bar/pulls/123/comments${PR_COMMON_OPERATIONS_NOTE?`

${PR_COMMON_OPERATIONS_NOTE}`:""}