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
250279b40fe486d7312421c158bbd1db96f08aed
.vscode.d/claude/commands/commit-push-pr.md
Jim Myhrberg 250279b40f feat(claude/commands): add AGENTS.md/CLAUDE.md review step to commit-push-pr 
Ensure agent documentation stays in sync with code changes by
having the command review AGENTS.md and CLAUDE.md before committing.
Adds both files to the context section and inserts a new first step
that checks whether changes warrant documentation updates.

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

2.4 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
  • PR template (if exists): !cat .github/PULL_REQUEST_TEMPLATE.md 2>/dev/null || echo "No PR template found"
  • AGENTS.md (if exists): !cat AGENTS.md 2>/dev/null || echo "No AGENTS.md found"
  • CLAUDE.md (if exists): !cat CLAUDE.md 2>/dev/null || echo "No CLAUDE.md found"

Your Task

Based on the above changes:

  1. Check agent docs: Review the AGENTS.md and CLAUDE.md content above against the current changes. If the changes introduce new conventions, commands, architecture, or development patterns that should be documented (or invalidate existing documentation), update the relevant file as part of this commit. Only update if clearly warranted — don't add noise.
  2. 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>.
  3. 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.
  4. Push the branch to origin
  5. 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.
  6. 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.