jimeh/.vscode.d
1
0
Fork 0
mirror of https://github.com/jimeh/.vscode.d.git synced 2026-02-19 03:16:39 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity
Files
27330ceae14e63c3f609e0e882d1ba0f416892ab
.vscode.d/claude/commands/commit-push-pr.md
Jim Myhrberg 27330ceae1 feat(claude/commands): support staged-only commits and add git diff permission 
Allow commit commands to operate on only staged changes when requested,
rather than always staging everything. This enables more granular control
over what gets committed.

- Add `Bash(git diff:*)` to allowed-tools in both commit and
  commit-push-pr commands
- Add instructions to check staged changes with `git diff --staged`
  and skip staging additional files when asked for staged-only commits
- Restructure commit.md flow to clarify staged-only vs full commit

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

1.6 KiB
Raw Blame History

allowed-tools, description, source
allowed-tools description source
Bash(git checkout --branch:*), Bash(git branch:*), Bash(git add:*), Bash(git diff:*), 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. 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
  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.