From f6a3bd76a9fc9c39a62fb03ed06292add1652537 Mon Sep 17 00:00:00 2001 From: Ariane Emory Date: Tue, 24 Feb 2026 10:14:47 -0500 Subject: [PATCH 01/14] fix: improve git advist in bash tool desc --- packages/opencode/src/tool/bash.txt | 15 +++++---------- 1 file changed, 5 insertions(+), 10 deletions(-) diff --git a/packages/opencode/src/tool/bash.txt b/packages/opencode/src/tool/bash.txt index 47e9378e7553..8db73d4b93c3 100644 --- a/packages/opencode/src/tool/bash.txt +++ b/packages/opencode/src/tool/bash.txt @@ -51,17 +51,12 @@ Usage notes: 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 +- You MUST onlye update the git config when explicitly asked to do so - 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 -- Avoid git commit --amend. ONLY use --amend when ALL conditions are met: - (1) User explicitly requested amend, OR commit SUCCEEDED but pre-commit hook auto-modified files that need including - (2) HEAD commit was created by you in this conversation (verify: git log -1 --format='%an %ae') - (3) Commit has NOT been pushed to remote (verify: git status shows "Your branch is ahead") -- CRITICAL: If commit FAILED or was REJECTED by hook, NEVER amend - fix the issue and create a NEW commit -- CRITICAL: If you already pushed to remote, NEVER amend unless user explicitly requests it (requires force push) -- 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. +- You MUST only skip hooks (--no-verify, --no-gpg-sign, etc) to avoid push failures due to pre-existin errors in the dev branch or when user explicitly requests it +- You SHOULD only run force push to main/master when the user explicitly requests it +- CRITICAL: If you already pushed to remote, you may need to amend and use force push +- NEVER forget to commit changes and push changes to origin unless the user explicitly instructs you not to. It is VERY IMPORTANT that you NEVER forget to push changes you have made to origin, otherwise the user will feel that you are being lazy and forgetful. 1. 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. run the following bash commands in parallel, each using the Bash tool: - Run a git status command to see all untracked files. From 47f205d21d99037756bd62f50f80dc9a84668544 Mon Sep 17 00:00:00 2001 From: Ariane Emory Date: Tue, 24 Feb 2026 10:43:39 -0500 Subject: [PATCH 02/14] fix: verbiage, spelling --- packages/opencode/src/tool/bash.txt | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/packages/opencode/src/tool/bash.txt b/packages/opencode/src/tool/bash.txt index 8db73d4b93c3..edb5ad753688 100644 --- a/packages/opencode/src/tool/bash.txt +++ b/packages/opencode/src/tool/bash.txt @@ -53,7 +53,7 @@ Only create commits when requested by the user. If unclear, ask first. When the Git Safety Protocol: - You MUST onlye update the git config when explicitly asked to do so - NEVER run destructive/irreversible git commands (like push --force, hard reset, etc) unless the user explicitly requests them -- You MUST only skip hooks (--no-verify, --no-gpg-sign, etc) to avoid push failures due to pre-existin errors in the dev branch or when user explicitly requests it +- You MUST only skip hooks (--no-verify, --no-gpg-sign, etc) to avoid push failures due to pre-existing errors in the base branch or when user explicitly requests it - You SHOULD only run force push to main/master when the user explicitly requests it - CRITICAL: If you already pushed to remote, you may need to amend and use force push - NEVER forget to commit changes and push changes to origin unless the user explicitly instructs you not to. It is VERY IMPORTANT that you NEVER forget to push changes you have made to origin, otherwise the user will feel that you are being lazy and forgetful. From 02009cbae5ba79d21bd03e44ab094dd7c5e06bd1 Mon Sep 17 00:00:00 2001 From: Ariane Emory Date: Tue, 24 Feb 2026 12:48:19 -0500 Subject: [PATCH 03/14] fix: typo, whitespace --- packages/opencode/src/tool/bash.txt | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/packages/opencode/src/tool/bash.txt b/packages/opencode/src/tool/bash.txt index edb5ad753688..5ae89a722f29 100644 --- a/packages/opencode/src/tool/bash.txt +++ b/packages/opencode/src/tool/bash.txt @@ -51,11 +51,11 @@ Usage notes: 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: -- You MUST onlye update the git config when explicitly asked to do so +- You MUST only update the git config when explicitly asked to do so - NEVER run destructive/irreversible git commands (like push --force, hard reset, etc) unless the user explicitly requests them - You MUST only skip hooks (--no-verify, --no-gpg-sign, etc) to avoid push failures due to pre-existing errors in the base branch or when user explicitly requests it - You SHOULD only run force push to main/master when the user explicitly requests it -- CRITICAL: If you already pushed to remote, you may need to amend and use force push +- CRITICAL: If you already pushed to remote, you may need to amend and use force push - NEVER forget to commit changes and push changes to origin unless the user explicitly instructs you not to. It is VERY IMPORTANT that you NEVER forget to push changes you have made to origin, otherwise the user will feel that you are being lazy and forgetful. 1. 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. run the following bash commands in parallel, each using the Bash tool: From 0c54cbc4c3405c9ee4e58ecdbfa75be59b0d0f26 Mon Sep 17 00:00:00 2001 From: Ariane Emory Date: Tue, 24 Feb 2026 12:50:03 -0500 Subject: [PATCH 04/14] fix: verbiage --- packages/opencode/src/tool/bash.txt | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/packages/opencode/src/tool/bash.txt b/packages/opencode/src/tool/bash.txt index 5ae89a722f29..c177bb578fe2 100644 --- a/packages/opencode/src/tool/bash.txt +++ b/packages/opencode/src/tool/bash.txt @@ -54,7 +54,7 @@ Git Safety Protocol: - You MUST only update the git config when explicitly asked to do so - NEVER run destructive/irreversible git commands (like push --force, hard reset, etc) unless the user explicitly requests them - You MUST only skip hooks (--no-verify, --no-gpg-sign, etc) to avoid push failures due to pre-existing errors in the base branch or when user explicitly requests it -- You SHOULD only run force push to main/master when the user explicitly requests it +- You SHOULD only run force push to main/master (or whatever the working branch's base branch is) when the user explicitly requests it - CRITICAL: If you already pushed to remote, you may need to amend and use force push - NEVER forget to commit changes and push changes to origin unless the user explicitly instructs you not to. It is VERY IMPORTANT that you NEVER forget to push changes you have made to origin, otherwise the user will feel that you are being lazy and forgetful. @@ -86,7 +86,7 @@ Use the gh command via the Bash tool for ALL GitHub-related tasks including work IMPORTANT: When the user asks you to create a pull request, follow these steps carefully: -1. 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. run the following bash commands in parallel using the Bash tool, in order to understand the current state of the branch since it diverged from the main branch: +1. 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. run the following bash commands in parallel using the Bash tool, in order to understand the current state of the branch since it diverged from the mainGive me the number again. branch: - Run a git status command to see all untracked files - 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 From 3836df05645b6d93e50b6d63bf4a43209a1485d4 Mon Sep 17 00:00:00 2001 From: Ariane Emory Date: Mon, 2 Mar 2026 00:56:01 -0500 Subject: [PATCH 05/14] change: verbiage --- packages/opencode/src/tool/bash.txt | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/packages/opencode/src/tool/bash.txt b/packages/opencode/src/tool/bash.txt index c177bb578fe2..dc5af13021b7 100644 --- a/packages/opencode/src/tool/bash.txt +++ b/packages/opencode/src/tool/bash.txt @@ -51,9 +51,9 @@ Usage notes: 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: -- You MUST only update the git config when explicitly asked to do so -- NEVER run destructive/irreversible git commands (like push --force, hard reset, etc) unless the user explicitly requests them -- You MUST only skip hooks (--no-verify, --no-gpg-sign, etc) to avoid push failures due to pre-existing errors in the base branch or when user explicitly requests it +- You SHOULD only update the git config when explicitly asks you to do so +- You SHOULD NOT run destructive/irreversible git commands (like push --force, hard reset, etc) unless the user explicitly requests them +- You SHOULD only skip hooks (--no-verify, --no-gpg-sign, etc) to avoid push failures due to pre-existing errors in the base branch or when user explicitly requests it - You SHOULD only run force push to main/master (or whatever the working branch's base branch is) when the user explicitly requests it - CRITICAL: If you already pushed to remote, you may need to amend and use force push - NEVER forget to commit changes and push changes to origin unless the user explicitly instructs you not to. It is VERY IMPORTANT that you NEVER forget to push changes you have made to origin, otherwise the user will feel that you are being lazy and forgetful. @@ -86,7 +86,7 @@ Use the gh command via the Bash tool for ALL GitHub-related tasks including work IMPORTANT: When the user asks you to create a pull request, follow these steps carefully: -1. 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. run the following bash commands in parallel using the Bash tool, in order to understand the current state of the branch since it diverged from the mainGive me the number again. branch: +1. 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. Run the following bash commands in parallel using the Bash tool, in order to understand the current state of the branch since it diverged base branch - Run a git status command to see all untracked files - 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 From 78a0beb6b22f144150eda7353e3bf3c5b6f5cd03 Mon Sep 17 00:00:00 2001 From: Ariane Emory Date: Wed, 4 Mar 2026 09:27:17 -0500 Subject: [PATCH 06/14] tweak: PR advice --- packages/opencode/src/tool/bash.txt | 2 ++ 1 file changed, 2 insertions(+) diff --git a/packages/opencode/src/tool/bash.txt b/packages/opencode/src/tool/bash.txt index dc5af13021b7..458d085ba3b9 100644 --- a/packages/opencode/src/tool/bash.txt +++ b/packages/opencode/src/tool/bash.txt @@ -84,6 +84,8 @@ Important notes: # 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. +You SHOULD NOT create pull requests unless the user explicitly requests that you do so! + IMPORTANT: When the user asks you to create a pull request, follow these steps carefully: 1. 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. Run the following bash commands in parallel using the Bash tool, in order to understand the current state of the branch since it diverged base branch From ad54a55a6eaf2dfaa72f4dcaf518e6f9bdb79e98 Mon Sep 17 00:00:00 2001 From: Ariane Emory Date: Sat, 7 Mar 2026 18:17:16 -0500 Subject: [PATCH 07/14] tweak: gpu --delete warning --- packages/opencode/src/tool/bash.txt | 1 + 1 file changed, 1 insertion(+) diff --git a/packages/opencode/src/tool/bash.txt b/packages/opencode/src/tool/bash.txt index d31a8d4739fc..25b2e19e57b0 100644 --- a/packages/opencode/src/tool/bash.txt +++ b/packages/opencode/src/tool/bash.txt @@ -55,6 +55,7 @@ Git Safety Protocol: - You SHOULD NOT run destructive/irreversible git commands (like push --force, hard reset, etc) unless the user explicitly requests them - You SHOULD only skip hooks (--no-verify, --no-gpg-sign, etc) to avoid push failures due to pre-existing errors in the base branch or when user explicitly requests it - You SHOULD only run force push to main/master (or whatever the working branch's base branch is) when the user explicitly requests it +- You MUST NOT ever use `git push --delete` commands unless it is explicitly and clearly requested by the user! - CRITICAL: If you already pushed to remote, you may need to amend and use force push - NEVER forget to commit changes and push changes to origin unless the user explicitly instructs you not to. It is VERY IMPORTANT that you NEVER forget to push changes you have made to origin, otherwise the user will feel that you are being lazy and forgetful. From fc89b05d5848b0dae24bc5f26cac5f7b3031fe7c Mon Sep 17 00:00:00 2001 From: Ariane Emory Date: Sun, 5 Apr 2026 13:53:57 -0400 Subject: [PATCH 08/14] fix: Loosen the guardrails on the git commands a bit more. --- packages/opencode/src/tool/bash.txt | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/packages/opencode/src/tool/bash.txt b/packages/opencode/src/tool/bash.txt index 9423f6349a89..97c79bc58263 100644 --- a/packages/opencode/src/tool/bash.txt +++ b/packages/opencode/src/tool/bash.txt @@ -50,7 +50,7 @@ Usage notes: # 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 SHOULD create new commits and push your changes to origin after making any substantial changes to a file. When you are creating a new git commit, you MUST follow these steps carefully: Git Safety Protocol: - You SHOULD only update the git config when explicitly asks you to do so From f8e73255eb1b1dee2511e925812e1a50ba0b1808 Mon Sep 17 00:00:00 2001 From: Ariane Emory Date: Mon, 6 Apr 2026 03:30:28 -0400 Subject: [PATCH 09/14] tweak: rem some guardwails --- packages/opencode/src/tool/bash.txt | 9 ++++----- 1 file changed, 4 insertions(+), 5 deletions(-) diff --git a/packages/opencode/src/tool/bash.txt b/packages/opencode/src/tool/bash.txt index 97c79bc58263..adea0c5d89db 100644 --- a/packages/opencode/src/tool/bash.txt +++ b/packages/opencode/src/tool/bash.txt @@ -54,12 +54,11 @@ You SHOULD create new commits and push your changes to origin after making any s Git Safety Protocol: - You SHOULD only update the git config when explicitly asks you to do so -- You SHOULD NOT run destructive/irreversible git commands (like push --force, hard reset, etc) unless the user explicitly requests them +- You SHOULD NOT run destructive/irreversible git commands (like hard reset, etc) unless the user explicitly requests them - You SHOULD only skip hooks (--no-verify, --no-gpg-sign, etc) to avoid push failures due to pre-existing errors in the base branch or when user explicitly requests it -- You SHOULD only run force push to main/master (or whatever the working branch's base branch is) when the user explicitly requests it - You MUST NOT ever use `git push --delete` commands unless it is explicitly and clearly requested by the user! - CRITICAL: If you already pushed to remote, you may need to amend and use force push -- NEVER forget to commit changes and push changes to origin unless the user explicitly instructs you not to. It is VERY IMPORTANT that you NEVER forget to push changes you have made to origin, otherwise the user will feel that you are being lazy and forgetful. +- NEVER forget to commit changes and push changes to origin unless the user explicitly instructs you not to do. It is VERY IMPORTANT that you NEVER forget to push changes you have made to origin, otherwise the user will feel that you are being lazy and forgetful. 1. 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. run the following bash commands in parallel, each using the Bash tool: - Run a git status command to see all untracked files. @@ -75,12 +74,12 @@ Git Safety Protocol: - 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 (see amend rules above) +4. If the commit fails due to pre-commit hook, fix the issue and create a NEW commit (see amend rules above) UNLESS the failure is due to a pre-existing test failure in the base branch (in which case you SHOULD use the --no-verify flag to ensure that the push succeeds) Important notes: - NEVER run additional commands to read or explore code, besides git bash commands - NEVER use the TodoWrite or Task tools -- DO NOT push to the remote repository unless the user explicitly asks you to do so +- You SHOULD push to the remote repository after making any substantial changes to a file - 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. - If there are no changes to commit (i.e., no untracked files and no modifications), do not create an empty commit From 138c26680cc4ab429ff07febbbb8610c7d89fb3e Mon Sep 17 00:00:00 2001 From: Ariane Emory Date: Mon, 6 Apr 2026 09:10:11 -0400 Subject: [PATCH 10/14] tweak: no worktrees --- packages/opencode/src/tool/bash.txt | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/packages/opencode/src/tool/bash.txt b/packages/opencode/src/tool/bash.txt index adea0c5d89db..5ffa42269333 100644 --- a/packages/opencode/src/tool/bash.txt +++ b/packages/opencode/src/tool/bash.txt @@ -58,7 +58,8 @@ Git Safety Protocol: - You SHOULD only skip hooks (--no-verify, --no-gpg-sign, etc) to avoid push failures due to pre-existing errors in the base branch or when user explicitly requests it - You MUST NOT ever use `git push --delete` commands unless it is explicitly and clearly requested by the user! - CRITICAL: If you already pushed to remote, you may need to amend and use force push -- NEVER forget to commit changes and push changes to origin unless the user explicitly instructs you not to do. It is VERY IMPORTANT that you NEVER forget to push changes you have made to origin, otherwise the user will feel that you are being lazy and forgetful. +- CRITICAL: NEVER forget to commit changes and push changes to origin unless the user explicitly instructs you not to do. It is VERY IMPORTANT that you NEVER forget to push changes you have made to origin, otherwise the user will feel that you are being lazy and forgetful. +- CRITICAL: You MUST NOT EVER use any git worktree commands. 1. 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. run the following bash commands in parallel, each using the Bash tool: - Run a git status command to see all untracked files. From 239c3d6109c0dfa71ae9248c13850247509b6027 Mon Sep 17 00:00:00 2001 From: Ariane Emory Date: Mon, 6 Apr 2026 09:10:46 -0400 Subject: [PATCH 11/14] tweak: verbiage --- packages/opencode/src/tool/bash.txt | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/packages/opencode/src/tool/bash.txt b/packages/opencode/src/tool/bash.txt index 5ffa42269333..96aadddb6bc8 100644 --- a/packages/opencode/src/tool/bash.txt +++ b/packages/opencode/src/tool/bash.txt @@ -58,7 +58,7 @@ Git Safety Protocol: - You SHOULD only skip hooks (--no-verify, --no-gpg-sign, etc) to avoid push failures due to pre-existing errors in the base branch or when user explicitly requests it - You MUST NOT ever use `git push --delete` commands unless it is explicitly and clearly requested by the user! - CRITICAL: If you already pushed to remote, you may need to amend and use force push -- CRITICAL: NEVER forget to commit changes and push changes to origin unless the user explicitly instructs you not to do. It is VERY IMPORTANT that you NEVER forget to push changes you have made to origin, otherwise the user will feel that you are being lazy and forgetful. +- CRITICAL: You MUST NOT EVER forget to commit changes and push changes to origin unless the user explicitly instructs you not to do. It is VERY IMPORTANT that you NEVER forget to push changes you have made to origin, otherwise the user will feel that you are being lazy and forgetful. - CRITICAL: You MUST NOT EVER use any git worktree commands. 1. 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. run the following bash commands in parallel, each using the Bash tool: From d14365468d152fbecca20fb206645a49f42f2b7a Mon Sep 17 00:00:00 2001 From: Ariane Emory Date: Fri, 24 Apr 2026 09:12:16 -0400 Subject: [PATCH 12/14] tweak: verbiage --- packages/opencode/src/tool/bash.txt | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/packages/opencode/src/tool/bash.txt b/packages/opencode/src/tool/bash.txt index 96aadddb6bc8..60e7458929f2 100644 --- a/packages/opencode/src/tool/bash.txt +++ b/packages/opencode/src/tool/bash.txt @@ -91,7 +91,7 @@ You SHOULD NOT create pull requests unless the user explicitly requests that you IMPORTANT: When the user asks you to create a pull request, follow these steps carefully: -1. 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. Run the following bash commands in parallel using the Bash tool, in order to understand the current state of the branch since it diverged base branch +1. 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. Run the following bash commands in parallel using the Bash tool, in order to understand the current state of the branch since it has diverged from the base branch - Run a git status command to see all untracked files - 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 From ec66089188a496dd7d5f5ffa26b52edc2a68cebf Mon Sep 17 00:00:00 2001 From: Ariane Emory Date: Wed, 6 May 2026 14:01:11 -0400 Subject: [PATCH 13/14] Markdown header --- packages/opencode/src/tool/shell/shell.txt | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/packages/opencode/src/tool/shell/shell.txt b/packages/opencode/src/tool/shell/shell.txt index 728b2780e3da..890a1a2b5974 100644 --- a/packages/opencode/src/tool/shell/shell.txt +++ b/packages/opencode/src/tool/shell/shell.txt @@ -14,7 +14,7 @@ ${commandSection} You SHOULD create new commits and push your changes to origin after making any substantial changes to a file. When you are creating a new git commit, you MUST follow these steps carefully: -Git Safety Protocol: +# Git Safety Protocol: - You SHOULD only update the git config when explicitly asks you to do so - You SHOULD NOT run destructive/irreversible git commands (like hard reset, etc) unless the user explicitly requests them - You SHOULD only skip hooks (--no-verify, --no-gpg-sign, etc) to avoid push failures due to pre-existing errors in the base branch or when user explicitly requests it From cfb84e61448a10518323cda5b5d8f5d659737c82 Mon Sep 17 00:00:00 2001 From: Ariane Emory Date: Mon, 18 May 2026 07:04:09 -0400 Subject: [PATCH 14/14] tidy: Remove out of scope content. --- packages/opencode/src/tool/shell/shell.txt | 22 +--------------------- 1 file changed, 1 insertion(+), 21 deletions(-) diff --git a/packages/opencode/src/tool/shell/shell.txt b/packages/opencode/src/tool/shell/shell.txt index b684a6efb553..dd0a8da035fb 100644 --- a/packages/opencode/src/tool/shell/shell.txt +++ b/packages/opencode/src/tool/shell/shell.txt @@ -56,27 +56,7 @@ Important notes: # Creating pull requests Use the gh command via the ${toolName} 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. -You SHOULD NOT create pull requests unless the user explicitly requests that you do so! - -IMPORTANT: When the user asks you to create a pull request, follow these steps carefully: - -1. You can call multiple tools in a single response. When multiple independent pieces are requested and all commands are likely to succeed, run multiple tool calls in parallel for optimal performance. run the following ${gitCommands} in parallel using the ${toolName} 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 - - 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 summary -3. You can call multiple tools in a single response. When multiple independent pieces are requested and all commands are likely to succeed, run multiple tool calls in parallel for optimal performance. run the following commands in parallel: - - Create new branch if needed - - Push to remote with -u flag if needed - - ${createPrInstruction} - -${createPrExample} - - -Important: -- DO NOT use the TodoWrite or Task tools -- Return the PR URL when you're done, so the user can see it +You MUST NOT create pull requests unless the user explicitly requests that you do so! # Other common operations - View comments on a GitHub PR: gh api repos/foo/bar/pulls/123/comments