skills.rest
kristofferremback
kristofferrembackCOMMUNITY
Explore all skills by this author →
GitHub

update-pr

Update GitHub pull request descriptions with structured problem and solution sections.

2|Updated Nov 15, 2025
Search Tags:#project management#documentation#collaboration#github#pr
One-click install
npx skills add https://github.com/kristofferremback/threa --skill update-pr-kristofferremback
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: update-pr
Source: https://github.com/kristofferremback/threa/tree/main/.claude/skills/update-pr
Command: npx skills add https://github.com/kristofferremback/threa --skill update-pr-kristofferremback

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates the manual updating of pull request descriptions, ensuring documentation stays in sync with code changes without manual editing.

Core Features & Use Cases

  • PR Description Updates: Automatically refresh and enhance pull request documentation.
  • Structured Templates: Apply consistent formatting with problem/solution frameworks.
  • Use Case: After making significant changes to a feature branch, use this Skill to automatically update the PR description to reflect the latest implementation.

Quick Start

Update the description of pull request #42 to include the new validation logic and updated test coverage.

Frequently Asked Questions about update-pr

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automatically update a pull request description on GitHub?▼

Update PR descriptions automatically by reading existing PR details via GitHub CLI, generating formatted content with structured sections like Problem and Solution, writing to a temporary file, and applying changes with gh pr edit. This keeps documentation synchronized with code changes without manual editing.

Can I apply consistent formatting templates to pull request bodies?▼

Yes. This Skill applies structured templates with problem/solution frameworks to PR descriptions, ensuring consistent formatting across GitHub repositories. It generates formatted bodies using printf-based steps and updates PR content while maintaining template structure.

When should I refresh a pull request description after code changes?▼

Refresh PR descriptions after making significant changes to a feature branch to reflect the latest implementation, new validation logic, updated test coverage, or design decisions. Automated updates eliminate manual syncing and keep documentation current with code.

What's the best way to manage PR documentation across multiple GitHub repositories?▼

Use automated PR description updates to standardize documentation across repositories. The Skill reads PR details via GitHub CLI, generates formatted bodies with consistent sections, and applies updates through the GitHub API or gh pr edit, reducing manual overhead.

Does this work with existing pull request content?▼

Yes. The Skill reads existing PR details and enhances them with updated information. It generates new formatted content, writes to a temporary file, updates the PR description, verifies the change, and cleans up temporary artifacts without losing prior context.

Related Skills

Explore More Software Engineering Skills→
dallaydallay

yeet

Publish local code changes to GitHub as a draft PR.

Official
Intermediate
OmniNode-aiOmniNode-ai
3

pr-watch

Monitor GitHub pull requests for review feedback and report terminal states.

Official
Advanced
taiga-Ktaiga-K
1

create-issue

Create GitHub issues from ISSUE_TEMPLATE files using the gh CLI.

Community
Basic
kamp-uskamp-us
25

report

Creates GitHub issues for flagged follow-up items via gh api.

Official
Advanced