skills.rest
cilly-yllic
cilly-yllicCOMMUNITY
Explore all skills by this author →
GitHub

__sync-pr

Synchronize a GitHub pull request title and body with the latest branch changes.

Updated May 13, 2026
Search Tags:#pull request#github#mermaid diagrams#cli automation#title update#body synchronization#diff-based editing
One-click install
npx skills add https://github.com/cilly-yllic/.llm --skill sync-pr-cilly-yllic
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: __sync-pr
Source: https://github.com/cilly-yllic/.llm/tree/main/skills/ja/__sync-pr
Command: npx skills add https://github.com/cilly-yllic/.llm --skill sync-pr-cilly-yllic

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

PRs often become outdated after additional commits, leaving the title and description inconsistent with what’s actually changed.

Core Features & Use Cases

  • Synchronizes PR content: Updates the existing Pull Request’s title and body to match the latest changes in the current branch.
  • Preserves user-added content: Performs section-level updates so manually added links, images, and notes are not lost.
  • Generates Mermaid diagrams when useful: Adds class diagrams, sequence diagrams, or CI/CD before/after workflow diagrams based on the type of changes.

Quick Start

Ask the AI to run /__sync-pr to refresh the current PR’s title and body using the latest branch diff.

Frequently Asked Questions about __sync-pr

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

FAQPage Schema
How do I update a GitHub pull request title and body after adding new commits?▼

To update a GitHub pull request after adding commits, synchronize the PR title and body with the latest branch changes. This process applies section-based diffs to refresh the description while preserving manually added links and notes.

Can I automatically generate Mermaid diagrams in my PR description from code changes?▼

Yes, you can generate Mermaid diagrams in your PR description from code changes. The synchronization process identifies relevant updates and automatically adds class, sequence, or CI/CD workflow diagrams based on the specific type of diff.

How do I update PR content without losing manually added notes and images?▼

To update PR content without losing manually added notes, use section-based diff updates. This method preserves user-authored sections, ensuring custom links, images, and notes remain intact while synchronizing the latest branch changes.

What is the best way to keep a pull request description in sync with branch changes?▼

The best way to keep a pull request description in sync with branch changes is to use CLI automation that reads the current diff. It updates the PR body using GitHub edit tooling while respecting repository rules precedence.

Does synchronizing PR content respect existing repository rules and protections?▼

Yes, synchronizing PR content respects existing repository rules and protections. The update process explicitly follows repository rules precedence when modifying the title and body through the GitHub PR edit tooling.

Why does my pull request title not match the latest branch diff?▼

Your pull request title does not match the latest branch diff because commits were added after PR creation. Synchronizing the PR with the current branch applies diff-based editing to align the title and body.

Related Skills

Explore More Software Engineering Skills→
joaquimscostajoaquimscosta
21

creating-pr

Create GitHub pull requests from feature branches using the GitHub CLI.

Community
Advanced
jimmymalhanjimmymalhan
1

rebase-manager

Rebase dependent pull request branches onto main after a base PR merges.

Community
Intermediate
antinomyhqantinomyhq
7.5k

create-pr-description

Generate pull request descriptions from branch diffs and create PRs via GitHub CLI.

Official
Intermediate
mParticlemParticle
7

pr

Create a GitHub pull request from the current branch with a conventional-commits-based title and descriptive body.

Official
Advanced