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

__resume-branch-context

Collect pull request, issue, and commit context for the current branch.

Updated May 13, 2026
Search Tags:#pull request#issue tracking#GitHub CLI#git diff#workflow resume#branch analysis#context restoration
One-click install
npx skills add https://github.com/cilly-yllic/.llm --skill resume-branch-context
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: __resume-branch-context
Source: https://github.com/cilly-yllic/.llm/tree/main/skills/ja/__resume-branch-context
Command: npx skills add https://github.com/cilly-yllic/.llm --skill resume-branch-context

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Branch work often starts with missing background, such as what a pull request says, what issues it references, and what changes have already been made, making it hard to pick up where you left off.

Core Features & Use Cases

  • PR context collection: Retrieves the current branch’s linked PR details (title, body, URL, state, reviews, comments) when a PR exists.
  • Issue number resolution: Attempts to identify the related issue number by cross-checking information found in the PR body and patterns inferred from the branch name, then applies a defined resolution policy.
  • Commit-progress summary: Compares commit history and diffs against the PR base branch (or the repository default/main/master when no PR exists) and summarizes progress and scope.

Quick Start

Ask the AI to run __resume-branch-context on your current branch to reconstruct the PR/issue context and summarize your changes.

Frequently Asked Questions about __resume-branch-context

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

FAQPage Schema
How do I restore branch context after an interruption to resume development?▼

To restore branch context, collect the current branch's pull request details, related issue content, and commit history. This resolves missing background information so you can verify what is implemented and resume work.

How do I find the related issue number from a pull request and branch name?▼

To find the related issue number, cross-check information found in the PR body and patterns inferred from the branch name. A defined resolution policy applies this cross-checking to accurately identify the linked issue.

How do I summarize commit progress against a pull request base branch?▼

To summarize commit progress, compare your commit history and git diffs against the PR base branch. If no PR exists, compare against the repository default branch to understand your development scope.

Can I use GitHub CLI to fetch pull request and issue data for my current branch?▼

Yes, you can use GitHub CLI (gh) to fetch pull request and issue data for your current branch. This retrieves PR details like title, state, and reviews, while resolving linked issues to restore context.

What if there is no pull request linked to my current branch?▼

If no pull request exists, the commit-progress summary compares your commit history and diffs against the repository default, main, or master branch. This still allows you to understand your changes and scope without an active PR.

Related Skills

Explore More Software Engineering Skills→
aivos-xieaivos-xie
1

github-pr-workflow

Automate the GitHub Pull Request lifecycle from branch creation to merging.

Community
Advanced
samuelmukotisamuelmukoti

github-code-review

Analyze git diffs and generate inline PR review comments.

Community
Advanced
ayazhankadessovaayazhankadessova

open-pr

Draft GitHub pull request titles and bodies from conversation context and code changes.

Community
Intermediate
DevQwietDevQwiet

create-pr

Generate GitHub pull request titles and descriptions from git logs and branch changes.

Community
Basic