From accelerator
Generates pull request descriptions following the repository's template. Fetches PR data and diffs via GitHub CLI, analyzes changes, runs verification commands.
npx claudepluginhub atomicinnovation/accelerator --plugin acceleratorThis skill is limited to using the following tools:
!`${CLAUDE_PLUGIN_ROOT}/scripts/config-read-context.sh`
Generates pull request descriptions from git diffs/commits with conventional titles, summaries, checklists, metadata, and reviewer tips to aid reviews.
Drafts conventional commit PR titles and Shopware 5-section descriptions for core PRs targeting trunk. Analyzes branch against trunk, uses session context, asks for missing info.
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.
Share bugs, ideas, or general feedback.
!${CLAUDE_PLUGIN_ROOT}/scripts/config-read-context.sh
!${CLAUDE_PLUGIN_ROOT}/scripts/config-read-skill-context.sh describe-pr
PRs directory: !${CLAUDE_PLUGIN_ROOT}/scripts/config-read-path.sh prs meta/prs
Tmp directory: !${CLAUDE_PLUGIN_ROOT}/scripts/config-read-path.sh tmp meta/tmp
IMPORTANT: Wherever {prs directory} or {tmp directory} appears in
the instructions below, substitute the actual resolved path shown above.
PR description template:
!${CLAUDE_PLUGIN_ROOT}/scripts/config-read-template.sh pr-description
You are tasked with generating a comprehensive pull request description following the repository's standard template.
gh pr view --json url,number,title,state 2>/dev/nullgh pr list --limit 10 --json number,title,headRefName,author{prs directory}/{number}-description.md already existsgh pr diff {number}gh repo set-default and select the appropriate repositorygh pr view {number} --json commitsgh pr view {number} --json baseRefNamegh pr view {number} --json url,title,number,statemake check test, npm test, etc.),
run it- [x]- [ ] with
explanationWrite the completed description to {prs directory}/{number}-description.md
with YAML frontmatter:
---
date: "{ISO timestamp}"
type: pr-description
skill: describe-pr
pr_number: {number}
pr_title: "{title}"
status: complete
---
{The generated PR description}
Show the user the generated description (without frontmatter — they'll see what gets posted to GitHub)
On re-run (when {prs directory}/{number}-description.md already exists),
regenerate the frontmatter with an updated date timestamp. The
existing step 3 already handles reading the prior description for
context; the frontmatter is simply regenerated fresh.
{prs directory}/{number}-description.md file contains YAML frontmatter
that should not appear on GitHub. Before posting, strip the frontmatter
block from the start of the file:
--- on line 1 and ends at the
next --- line (which closes the YAML block). Only match the
opening frontmatter block — do not match --- lines that appear
later in the body (e.g., markdown horizontal rules).mkdir -p {tmp directory}--- line to
{tmp directory}/pr-body-{number}.mdgh pr edit {number} --body-file {tmp directory}/pr-body-{number}.md{tmp directory}/pr-body-{number}.md!${CLAUDE_PLUGIN_ROOT}/scripts/config-read-skill-instructions.sh describe-pr