Menu
Creates a branch named from the work done, commits all changes with a detailed conventional-commit message, pushes to GitHub, and opens a PR (or updates the existing PR description if one already exists) whose title and body come directly from the commit message.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
An example custom skill.
An example custom skill version for demonstration.
Reviews the work just done and updates CLAUDE.md, agent memories, and subagent MD files to reflect any new conventions, packages, resources, or patterns discovered. Run after completing any significant implementation task.
Plans and scaffolds Anthropic API endpoints as Terraform resources/data sources without a task management tool. TRIGGER when: user says "implement GitHub issues", references a range of GitHub issues to implement (e.g. "issues 52 to 57"), asks to parallelize implementation of multiple resources/data sources, or says "implement all [API name] APIs" or "work on a new API" (e.g. /v1/skills, /v1/environments). Generates GitHub issues and branches if they to not already exist — one per resource/data source — ready for sequential or parallel implementation.
Plans and scaffolds Anthropic API endpoints as Terraform resources/data sources for Vibe Kanban. TRIGGER when: user says "implement GitHub issues", references a range of GitHub issues to implement (e.g. "issues 52 to 57"), asks to parallelize implementation of multiple resources/data sources, or says "implement all [API name] APIs". Creates Vibe Kanban issues, workspaces, and fires parallel agents — one per resource/data source.
Updates the GitHub PR description for the current branch based on the work done in the current Claude session. Use after any meaningful change to a PR (feature, fix, refactor, docs). Invoked automatically when Claude stops if an open PR exists for the current branch. Also works inside Vibe Kanban worktrees (vk/* branches) by resolving the PR via the VK issue context.
| name | ship |
| description | Creates a branch named from the work done, commits all changes with a detailed conventional-commit message, pushes to GitHub, and opens a PR (or updates the existing PR description if one already exists) whose title and body come directly from the commit message. |
| model | sonnet |
Turn local changes into a PR-ready branch in four steps: branch → commit → push → PR.
Run in a single parallel message:
git status
git diff HEAD
git log main..HEAD --oneline
Read any changed files you haven't already seen in this session. The goal is to understand what changed and why well enough to write an accurate commit message.
If already on a non-main/non-master branch, skip this step.
Derive a branch name from the work:
<type>/<short-description> (e.g. fix/environment-updated-at-plan-modifier)feat, fix, refactor, docs, test, ci, choregit checkout -b <branch-name>
Stage all relevant changed files (be explicit — avoid git add -A if untracked files might be sensitive) and create a commit with a conventional commit message:
<type>(<optional scope>): <imperative summary> — 72 characters maxgit add <files>
git commit -m "$(cat <<'EOF'
<type>(<scope>): <summary>
<body>
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
EOF
)"
Push the branch:
git push -u origin <branch-name>
Then check whether an open PR already exists for this branch:
gh pr list --head "$(git rev-parse --abbrev-ref HEAD)" --state open --json number,url \
--jq 'if length > 0 then "\(.[0].number) \(.[0].url)" else "" end'
If no open PR exists — write the body to a temp file, then create the PR. The title must be the commit title (first line, without the Co-Authored-By trailer). The body must be the commit body. Write each bullet as a single unbroken line — do not hard-wrap at 80 chars, as continuation lines render as visible line breaks on GitHub.
cat > /tmp/pr_body.txt << 'ENDBODY'
<commit body>
🤖 Generated with [Claude Code](https://claude.com/claude-code)
ENDBODY
gh pr create \
--title "<commit title>" \
--body-file /tmp/pr_body.txt
If an open PR already exists — synthesise an updated description from all commits on this branch since main, then update the PR via the GitHub API (gh pr edit can fail with a Projects classic deprecation error). Write each bullet as a single unbroken line — do not hard-wrap at 80 chars.
git log main..HEAD --format="%s%n%n%b" # all commit titles + bodies
cat > /tmp/pr_body.txt << 'ENDBODY'
<consolidated summary of all changes>
🤖 Generated with [Claude Code](https://claude.com/claude-code)
ENDBODY
gh api repos/{owner}/{repo}/pulls/<number> \
--method PATCH \
--raw-field title="<title reflecting all commits>" \
--raw-field body="$(cat /tmp/pr_body.txt)" \
--jq '.html_url'
Report the PR URL to the user.
Then write the sentinel file to suppress the stop hook (which would otherwise ask you to run /update-pr-description on a PR whose description is already correct):
branch=$(git rev-parse --abbrev-ref HEAD 2>/dev/null)
touch "/tmp/claude-pr-desc-done-$(echo "$branch" | tr '/' '-')"