pr | dev | ClaudePluginHub

Skill

pr

From dev

Create or update a pull request for the current branch with a summary of all changes.

$

npx claudepluginhub derogab/agent-kit --plugin git

Tool Access

This skill uses the workspace's default tool permissions.

Preview

- Current branch: !`git branch --show-current`

SKILL.md

Similar Skills

skill-lookup

159.9k

Searches, retrieves, and installs Agent Skills from prompts.chat registry using MCP tools like search_skills and get_skill. Activates for finding skills, browsing catalogs, or extending Claude.

prompt-lookup

159.9k

Searches prompts.chat for AI prompt templates by keyword or category, retrieves by ID with variable handling, and improves prompts via AI. Use for discovering or enhancing prompts.

next-compile

139.2k

Checks Next.js compilation errors using a running Turbopack dev server after code edits. Fixes actionable issues before reporting complete. Replaces `next build`.

1 file

vercel-next-js-2

Stats

Stars4

Forks0

Last CommitMar 11, 2026

Actions

View Source View Plugin View on GitHub View README

Context

Current branch: !git branch --show-current
Base branch: !if git rev-parse --verify main >/dev/null 2>&1; then echo main; else echo master; fi
Commits on this branch (since base): !if git rev-parse --verify main >/dev/null 2>&1; then git log --oneline main..HEAD; else git log --oneline master..HEAD; fi
PR for this branch: !gh pr view --json number,title,url 2>/dev/null || echo "NO_PR"

Your task

Create or update a pull request for the current branch.

Pre-flight checks

If the current branch is the base branch, stop and tell the user to switch to a feature branch first. Do nothing else.
If there are no commits ahead of the base branch, stop and tell the user to commit changes first. Do nothing else.
Never run git add or git commit. Only manage the PR.

Analysis

Run git diff <base>...HEAD to get the full diff of all changes on this branch.
Run git log <base>..HEAD --format="%h %s" to get all commit messages.
Identify the main topic, group specific changes logically.

Decide: create or update

If the PR context above shows NO_PR → create a new PR.
If a PR is found for the current branch → update that PR.

PR title

Follow Conventional Commits format: <type>: <description>.

Types: feat, fix, docs, refactor, test, chore, build, perf, ci. Append ! for breaking changes.

When updating, keep the existing title unless it is generic (e.g. "Update"), outdated, or does not follow Conventional Commits.

PR body format

## Summary
<1-2 sentence high-level description of what this PR does and why>

## Changes
<bulleted list of all meaningful changes, grouped logically>

## Test plan
<bulleted checklist of how to verify these changes>

Execution

Create flow:

Push the branch to origin: git push -u origin <branch>.
Create the PR: gh pr create --title "<title>" --body "<body>".

Update flow:

Update the PR: gh pr edit --title "<title>" --body "<body>".

Rules

Write the summary in plain English, focusing on the why and the what.
List changes as concise bullet points. Group related items under sub-headers if the PR touches multiple areas.
The test plan should contain actionable verification steps relevant to the changes. If a check was already run and passed, mark it as done.
Use a HEREDOC to pass the body to gh pr create or gh pr edit.
Do not send any text besides the tool calls.