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

feat(claude/commands): improve commit-push-pr with PR template and master branch support

Browse Source 
Add PR template auto-detection context, handle master as a default
branch alongside main, and use template content for PR body when
available.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
This commit is contained in:
Jim Myhrberg
2026-02-08 19:26:02 +00:00
parent 3f25c7e4fe
commit 6297f5b61d
1 changed files with 11 additions and 7 deletions
Download Patch File Download Diff File Expand all files Collapse all files

18
claude/commands/commit-push-pr.md
View File

@@ -9,22 +9,26 @@ source: https://github.com/anthropics/claude-plugins-official/blob/main/plugins/
- Current git status: !`git status`
- Current git diff (staged and unstaged changes): !`git diff HEAD`
- Current branch: !`git branch --show-current`
- PR template (if exists): !`cat .github/PULL_REQUEST_TEMPLATE.md 2>/dev/null || echo "No PR template found"`
## Your task
## 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>`.
1. Create a new branch if on main or master. If already on a non-main/master
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. If asked to commit only
staged changes, run `git diff --staged` to see exactly what is staged, and
base the commit message solely on those changes. Do NOT stage additional
files. Otherwise, stage all relevant changes.
3. Push the branch to origin
4. Create a pull request using `gh pr create`
4. Create a pull request using `gh pr create`. If a PR template exists in the
context above, use it as the base for the PR body and fill in the sections
appropriately based on the changes.
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