jimeh/.vscode.d
1
0
Fork 0
mirror of https://github.com/jimeh/.vscode.d.git synced 2026-02-19 11:26:39 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity
Files
623e3896e6adbfbedf6d8a7ab1b1f7471133a6f2
.vscode.d/claude/commands/commit-push-pr.md
Jim Myhrberg 623e3896e6 fix(claude/commands): improve line wrapping for 80-char line length 
Reflow long lines in command files to stay within 80 characters,
matching the project's line length convention. Also fix lowercase
"markdown" to "Markdown" in refactor-agents.md.md.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
2026-02-08 17:22:22 +00:00

1.3 KiB
Raw Blame History

allowed-tools, description, source
allowed-tools description source
Bash(git checkout --branch:*), Bash(git branch:*), Bash(git add:*), Bash(git status:*), Bash(git push:*), Bash(git commit:*), Bash(gh pr create:*) Commit, push, and open a PR, rename branch appropriately if needed https://github.com/anthropics/claude-plugins-official/blob/main/plugins/commit-commands/commands/commit-push-pr.md

Context

  • Current git status: !git status
  • Current git diff (staged and unstaged changes): !git diff HEAD
  • Current branch: !git branch --show-current

Your task

Based on the above changes:

  1. Create a new branch if on main. If already on a non-main branch, check if the branch name looks randomly generated (e.g. UUIDs, hex strings, meaningless character sequences, or 1-3 random unrelated words like "brave-fox" or "purple-mountain") rather than descriptive of the changes. If so, rename it to something that aligns with the changes using git branch -m <new-name>.
  2. Create a single commit with an appropriate message
  3. Push the branch to origin
  4. Create a pull request using gh pr create
  5. You have the capability to call multiple tools in a single response. You MUST do all of the above in a single message. Do not use any other tools or do anything else. Do not send any other text or messages besides these tool calls.