Generate PR description from changes and plan context — summary, changes, test plan, breaking changes
Generates structured PR descriptions from git changes and task plans with summaries, change lists, and test checklists.
npx claudepluginhub jugrajsingh/skillgardenThis skill is limited to using the following tools:
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}
Expert guidance for Next.js Cache Components and Partial Prerendering (PPR). **PROACTIVE ACTIVATION**: Use this skill automatically when working in Next.js projects that have `cacheComponents: true` in their next.config.ts/next.config.js. When this config is detected, proactively apply Cache Components patterns and best practices to all React Server Component implementations. **DETECTION**: At the start of a session in a Next.js project, check for `cacheComponents: true` in next.config. If enabled, this skill's patterns should guide all component authoring, data fetching, and caching decisions. **USE CASES**: Implementing 'use cache' directive, configuring cache lifetimes with cacheLife(), tagging cached data with cacheTag(), invalidating caches with updateTag()/revalidateTag(), optimizing static vs dynamic content boundaries, debugging cache issues, and reviewing Cache Component implementations.
Creating algorithmic art using p5.js with seeded randomness and interactive parameter exploration. Use this when users request creating art using code, generative art, algorithmic art, flow fields, or particle systems. Create original algorithmic art rather than copying existing artists' work to avoid copyright violations.