pull-request

pull-request

Generate a pull-request description from the commits on the current branch that diverge from a base branch. The description is saved to ./tmp/pull-request.md, following (in order of preference) a user override, the repo's GitHub PR template, or the skill's default template.

Arguments

• $1 — base branch to compare against (default: dev). Examples: dev, main, origin/main.
• $2 — output language (default: en). Examples: en, pt-BR.

Flow

1. Resolve arguments. branch = $1 || dev, language = $2 || en.

2. Capture the diff.

   git log --patch --graph <branch>..
   

3. Save the diff for inspection.

   mkdir -p ./tmp
   

   Write the output of step 2 to ./tmp/diff.txt.

4. Resolve the PR template in this order (stop at the first found):

   1. ./tmp/templates/pull-request.md — user project override
   2. GitHub convention, checked in this order:
      • .github/pull_request_template.md
      • .github/PULL_REQUEST_TEMPLATE.md
      • .github/pull_request_template/ or .github/PULL_REQUEST_TEMPLATE/ — if it is a directory, use the first *.md inside (check with Glob pattern .github/{pull_request_template,PULL_REQUEST_TEMPLATE}/*.md).
   3. ${CLAUDE_PLUGIN_ROOT}/skills/pull-request/template.md — plugin default

   Use Read on each candidate in order. The first existing file wins.

5. Generate the PR description following the resolved template:

   • Fill every section of the template using what the diff from step 2 actually shows. Do not invent content; if a section cannot be filled from the diff, keep the heading with a brief honest placeholder like N/A or a single-line summary.
   • Use simple, clear, objective, concise language.
   • Markdown output.
   • Written in $2 language.
   • Write only what fits the description — no long commit-by-commit walkthroughs.

   If the skill default (template 4.iii) is the active template, follow its format exactly: the title line must be tagged as # [Feat|Fix|Refactor|Test|Chore|Docs|Style|Perf|Build|CI|Revert|WIP] <title>, with sections ## Context, ## Changes, ## Observations.

6. Save the description. Write the final markdown to ./tmp/pull-request.md.

7. Report back in plain text (in $2 language):

   • Which template was used (the file path).
   • The diff file path (./tmp/diff.txt).
   • The PR description file path (./tmp/pull-request.md).