From shipit
Use when a branch is ready for PR creation and needs a structured description from diff and plan context
npx claudepluginhub jugrajsingh/skillgarden --plugin shipitThis skill is limited to using the following tools:
Generate a structured PR description from branch changes and plan context, then create the PR.
Guides Next.js Cache Components and Partial Prerendering (PPR) with cacheComponents enabled. Implements 'use cache', cacheLife(), cacheTag(), revalidateTag(), static/dynamic optimization, and cache debugging.
Guides building MCP servers enabling LLMs to interact with external services via tools. Covers best practices, TypeScript/Node (MCP SDK), Python (FastMCP).
Generates original PNG/PDF visual art via design philosophy manifestos for posters, graphics, and static designs on user request.
Generate a structured PR description from branch changes and plan context, then create the PR.
$ARGUMENTS = optional base branch. Defaults to develop.
Run these commands to understand what this PR contains:
Commit history:
git log {base}...HEAD --oneline
File change summary:
git diff {base}...HEAD --stat
Full diff for analysis:
git diff {base}...HEAD
Current branch:
git branch --show-current
If the diff is empty (no changes vs base), report "No changes found between {branch} and {base}. Nothing to create a PR for." and stop.
Task plan context:
Design docs:
Commit message context:
Build the PR description with these sections:
Derive from branch name or plan title:
1-3 bullet points describing:
Group changes by type based on commit prefixes:
List each change as a bullet point with brief description.
Derive from acceptance criteria:
If task_plan.md exists: convert acceptance criteria to checklist items
If no plan: extract testable claims from commit messages
Format as bulleted markdown checklist:
- [ ] Criterion 1 description
- [ ] Criterion 2 description
Scan for breaking changes:
Output the full PR description draft.
Ask via AskUserQuestion:
If user chose to create:
Ensure branch is pushed:
git push -u origin {branch_name}
Create the PR using gh CLI with HEREDOC for the body:
gh pr create --title "{title}" --body "$(cat <<'EOF'
{full PR body}
EOF
)" --base {base}
Capture and report the PR URL.
Output:
## PR Created
URL: {pr_url}
Title: {title}
Base: {base} <- {branch}