git-pr-recovery

Recover GitHub pull request branches using safe worktrees without disturbing local changes.

18|3|Updated Jul 3, 2020

Search Tags:#git #workflow #recovery #branch #pr

Ready to run

npx skills add https://github.com/jguadagno/jjgnet-broadcast --skill git-pr-recovery

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: git-pr-recovery
Source: https://github.com/jguadagno/jjgnet-broadcast/tree/main/.squad/skills/git-pr-recovery
Command: npx skills add https://github.com/jguadagno/jjgnet-broadcast --skill git-pr-recovery

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill enables developers to recover and push fixes onto existing pull request branches while maintaining the integrity of their local environment, preventing accidental overwrites or conflicts.

Core Features & Use Cases

Branch Recovery: Uses dedicated worktrees to repair issue-scoped branches with uncommitted or missing changes.
Workflow Enhancement: Facilitates safe communication with review teams by posting comments or notes after recovery.
Use Case: Imagine a developer needs to fix issues in a pull request branch that has uncommitted local changes; this Skill automates the process of creating a safe workspace, applying the fixes, and notifying reviewers seamlessly.

Quick Start

Use the git-pr-recovery skill to repair a branch with issues and post a recovery note on GitHub.

Frequently Asked Questions about git-pr-recovery

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

FAQPage Schema

How do I update a GitHub pull request branch without losing local uncommitted changes?▼

To update a GitHub pull request branch without losing local uncommitted changes, the git-pr-recovery skill creates a dedicated safe workspace using git worktrees. This isolates the branch recovery process, copying issue-scoped files and pushing remote updates without overwriting your current local environment.

What is the best way to recover a missing or broken pull request branch?▼

The best way to recover a broken pull request branch is using an automated recovery tool that generates a safe worktree. This approach repairs the issue-scoped branch and updates the remote repository without disrupting your existing local workspace or causing accidental file conflicts.

Can I push fixes to an existing GitHub PR while keeping my current workspace intact?▼

Yes, you can push fixes to an existing GitHub PR while keeping your workspace intact. The git-pr-recovery skill facilitates this by creating an isolated worktree to apply the changes, ensuring your local uncommitted work remains completely undisturbed during the update.

How do I notify reviewers after recovering a pull request branch?▼

To notify reviewers after recovering a pull request branch, the git-pr-recovery skill includes workflow enhancement features that automatically post comments or recovery notes directly on GitHub. This ensures seamless communication with the review team immediately after the branch is updated.

Does git worktree isolation work for automating pull request branch updates?▼

Yes, git worktree isolation works effectively for automating pull request branch updates. The git-pr-recovery skill leverages this mechanism to safely create dedicated workspaces, allowing developers to apply issue-scoped fixes and push remote branch updates without risking local environment overwrites.

When should I avoid directly checking out a pull request branch for recovery?▼

You should avoid directly checking out a pull request branch for recovery when you have local uncommitted changes that could be overwritten. Using an isolated worktree instead prevents accidental conflicts and maintains the integrity of your primary local development environment.