Skip to content
Skills Library
Programming · Writing

github-pr-body

/github-pr-body

Update PR body content with deterministic baseline sections and optional full-body completion. Use when creating PRs or regenerating template-driven summaries.

Licence
Apache-2.0
Last repository change
18.10.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
28
Scripts
12
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 18.10.2026, without references to retired models or APIs.

Licence

Apache-2.0, otwarta: można używać i zmieniać, z zachowaniem licencji i informacji o zmianach.

What to check before installing
  • 12 scripts in this package. Review them before installing, as Claude may execute them.

Scripts: scripts/lib/all.sh, scripts/lib/aws.sh, scripts/lib/common.sh, scripts/lib/csv.sh, scripts/lib/json.sh, scripts/lib/repo_paths.sh, scripts/lib/terraform.sh, scripts/lib/validation.sh, scripts/lib/yaml_map_order.py, scripts/pr_body.sh, scripts/pr_comment.sh, scripts/pr_fetch.sh

What it does and when to use it

Update PR body content with deterministic baseline sections and optional full-body completion. Use when creating PRs or regenerating template-driven summaries.

Original author description

Update PR body content with deterministic baseline sections and optional full-body completion. Use when creating PRs or regenerating template-driven summaries.

How it works

  1. Input
  2. Output Specification
  3. Execution Scope
  4. Reference Files Guide
  5. Workflow
Original SKILL.md headings · 115 lines, 599 words
SKILL.md preview
---
name: github-pr-body
description: >-
  Update PR body content with deterministic baseline sections and optional full-body completion.
  Use when creating PRs or regenerating template-driven summaries.
license: Apache-2.0
metadata:
  author: y-miyazaki
  version: "1.0.2"
---

## Input

- PR number and `owner/repo` (required)
- Existing PR template/body context (required)
- Authenticated `gh` environment (required)

## Output Specification

Return structured Markdown in accordance with [references/common-output-format.md](references/common-output-format.md).

Structured PR output:

- Baseline mode: update `## Overview` and `## Changes`.
- Full-body mode: apply complete body via `--body-file`.
- `## Changes` must classify files (Config/Docs/Feature/Test/Other) with line counts.
- Report selected mode and reason.

## Execution Scope

- **Always use `scripts/pr_body.sh` or `scripts/pr_fetch.sh`**. Do not run individual `gh` commands.
- `pr_body.sh` is deterministic and idempotent.

### USE FOR:

- generate deterministic baseline PR body sections
- regenerate PR body from template sections after code updates
- fill remaining sections in full-body mode from validated context

### DO NOT USE FOR:

- post review comments or resolve review threads
- create commits or modify source files
- replace issue triage workflows

## Reference Files Guide

- [common-checklist.md](references/common-checklist.md) (always read)
- [common-output-format.md](references/common-output-format.md) (always read)
- [common-troubleshooting.md](references/common-troubleshooting.md) (read on failure)
- [category-pr-body-guidelines.md](references/category-pr-body-guidelines.md) (read when full-body mode)
- [category-template-mapping.md](references/category-template-mapping.md) (read when full-body mode)
- [category-change-classification.md](references/category-change-classification.md) (read when classifying changes)
- [category-command-reference.md](references/category-command-reference.md) (read on debugging)
- [category-implementation-details.md](references/category-implementation-details.md) (read on debugging)
- [category-agent-workflows.md](references/category-agent-workflows.md) (read on debugging)

## Workflow

1. Fetch PR metadata:

   ```bash
   scripts/pr_fetch.sh <PR_NUMBER> --repo <OWNER/REPO>
   ```

   Parse JSON output to obtain: title, body, file list, additions/deletions, headRefName, baseRefName.

2. Generate deterministic baseline (`## Overview`, `## Changes`):

   ```bash
   scripts/pr_body.sh <PR_NUMBER> --repo <OWNER/REPO> --dry-run
   ```

   Review dry-run output. If acceptable, apply:

   ```bash
   scripts/pr_body.sh <PR_NUMBER> --repo <OWNER/REPO>
   ```

3. Select mode:

   - Baseline mode: request scope is summary refresh only → skip to Step 6.
   - Full-body mode: request explicitly asks to populate all template sections → continue to Step 4.

4. Generate AI-completed content (full-body mode only):

   1. Read [category-pr-body-guidelines.md](references/category-pr-body-guidelines.md). Read [category-template-mapping.md](references/category-template-mapping.md) when template comment guidance is ambiguous.
   2. Read `.github/PULL_REQUEST_TEMPLATE.md` from the repository.
   3. For each H2 section in the template:
      - If the section comment contains an `Example:` block, follow that structure to generate visible content.
      - If the section comment contains checkbox guidance, generate or update checkbox lines in the same format.
      - If the section has no guidance, preserve the section heading and template comment without inventing content.
   4. Keep `## Overview` and `## Changes` content from Step 2 output.
   5. Write the complete PR body (all sections) to a temporary file (e.g., `/tmp/completed_pr_body.md`).

5. Apply full body (full-body mode only):

   ```bash
   scripts/pr_body.sh <PR_NUMBER> --repo <OWNER/REPO> --body-file /tmp/completed_pr_body.md
   ```

6. Verify success:
   ```bash
   gh pr view <PR_NUMBER> --repo <OWNER/REPO> --json body --jq '.body'
   ```
   Confirm `## Overview` and `## Changes` sections are present and non-empty. In full-body mode, confirm `## Testing`, `## Type of Change`, `## Checklist`, and `## Additional Notes` contain visible content.

### Error Handling

| Condition                                  | Severity    | Action                                               |
| ------------------------------------------ | ----------- | ---------------------------------------------------- |
| `gh` not authenticated                     | Fatal       | Stop; instruct `gh auth login`                       |
| PR not found (404)                         | Fatal       | Verify PR number and `owner/repo`                    |
| Access denied (403)                        | Fatal       | Verify `repo` write scope                            |
| `pr_fetch.sh` or `pr_body.sh` missing      | Fatal       | Stop; report missing script                          |
| `.github/PULL_REQUEST_TEMPLATE.md` missing | Recoverable | Baseline mode only; skip full-body template sections |
| Body exceeds GitHub size limit (422)       | Recoverable | Truncate or split content; report in output          |
| Rate limit exceeded (429)                  | Recoverable | Defer update; note retry window in report            |
| Dry-run output unacceptable                | Info        | Do not apply; report diff issues and stop            |

### Examples

- Prompt: `Generate PR body for PR #42`
- Result: PR body updated via `scripts/pr_body.sh`; report mode and reason per [references/common-output-format.md](references/common-output-format.md).
Files in this package (28)
  • SKILL.md 6 KB
  • eval.yaml 1 KB
  • evals/tasks/github-pr-body-basic.yaml 1 KB
  • evals/tasks/github-pr-body-boundary-guardrail.yaml 1 KB
  • evals/tasks/github-pr-body-multi-file-changes.yaml 1 KB
  • evals/tasks/github-pr-body-structured-output.yaml 1 KB
  • evals/tasks/github-pr-body-trigger-negative.yaml 1 KB
  • references/category-agent-workflows.md 6 KB
  • references/category-change-classification.md 10 KB
  • references/category-command-reference.md 9 KB
  • references/category-implementation-details.md 8 KB
  • references/category-pr-body-guidelines.md 13 KB
  • references/category-template-mapping.md 14 KB
  • references/common-checklist.md 1 KB
  • references/common-output-format.md 2 KB
  • references/common-troubleshooting.md 10 KB
  • scripts/pr_body.sh 28 KB
  • scripts/pr_comment.sh 8 KB
  • scripts/pr_fetch.sh 9 KB
  • scripts/lib/all.sh 1 KB
  • scripts/lib/aws.sh 29 KB
  • scripts/lib/common.sh 9 KB
  • scripts/lib/csv.sh 4 KB
  • scripts/lib/json.sh 8 KB
  • scripts/lib/repo_paths.sh 15 KB
  • scripts/lib/terraform.sh 13 KB
  • scripts/lib/validation.sh 14 KB
  • scripts/lib/yaml_map_order.py 6 KB

Versions

The database has no other skills named github-pr-body.

Identical content appears in 1 other GitHub folders. We show one copy with the highest score.

Database snapshot: 13.11.2026 · package version 34730f804e27 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100update-pr-body
    Update the body of a GitHub pull request. Use when the user asks to update, edit, or modify a PR description/body.
  • 100pr-description
    Render the canonical PR description body. Use when drafting, writing, updating, or regenerating a "PR description", "PR body", "pull request description", "pull request body", "PR summary", "PR template", "GitHub PR body", or any text bound for `gh pr create --body`, `gh pr…
  • 100pr
    Write or update a pull request body from the repo's PR template, with evidence and validation traced to commands actually run. Use when writing or updating a PR body. To open the PR itself, use file-pr.
  • 100pr-style
    This skill should be used when creating or editing a GitHub pull request title or description, regardless of tool (gh CLI, GitHub MCP tools, API). Defines PR title format and body format with Why/What/Notes sections.
  • 86update-pr-summary
    This skill should be used when user asks to "update PR summary", "update PR description", "rewrite PR body", "refresh PR title and body", or explicitly invokes "update-pr-summary".
  • 96pr
    The shape of a pull request body. Use when writing or editing a PR description.

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.