uplift

Create uplift pull requests by cherry-picking test and crash fixes from closed PRs.

4|Updated Feb 2, 2026
One-click install
npx skills add https://github.com/brave-experiments/brave-core-bot --skill uplift
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: uplift
Source: https://github.com/brave-experiments/brave-core-bot/tree/main/.claude/skills/uplift
Command: npx skills add https://github.com/brave-experiments/brave-core-bot --skill uplift

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill automates the creation of uplift pull requests, ensuring critical fixes and improvements are efficiently merged into target branches like beta or release.

Core Features & Use Cases

  • Automated Cherry-Picking: Selectively picks commits from closed PRs based on defined criteria (test fixes, crash fixes).
  • Target Branch Integration: Creates PRs against specified branches (beta or release).
  • Use Case: A developer needs to quickly merge several intermittent test fixes from recent commits into the beta branch. They can use this Skill to automate the process of identifying, cherry-picking, and creating a PR for these fixes.

Quick Start

Use the uplift skill to create an uplift PR for the user 'netzenbot' targeting the beta branch, including PRs 33534, 33547, and 33580.

Frequently Asked Questions about uplift

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

FAQPage Schema
How do I automate cherry-picking commits from closed pull requests into a release branch?

Automating cherry-picking commits from closed pull requests involves selectively picking intermittent test fixes and crash fixes, then creating an uplift PR against a target branch. This Skill filters closed PRs by author, date range, or specific numbers to streamline integration.

What is an uplift pull request and when do I need to create one?

An uplift pull request merges critical fixes from closed PRs into target branches like beta or release. You need to create an uplift PR when selectively moving specific crash fixes or test improvements from a main branch into a stabilization branch.

How do I filter specific closed GitHub pull requests for cherry-picking into beta?

Filtering specific closed GitHub pull requests for cherry-picking is done by defining criteria like author username, date range, or specific PR numbers. This targets only the relevant crash fixes and test improvements for the uplift PR.

Do I need GitHub CLI and Git installed to automate pull request management for code integration?

Yes, you need Git and GitHub CLI installed to automate pull request management for code integration. The Skill integrates with GitHub CLI for PR creation and relies on Git for the cherry-picking process, while web fetching retrieves release schedules.

What's the best way to merge intermittent test fixes from multiple commits into a release branch?

The best way to merge intermittent test fixes from multiple commits into a release branch is automating the identification and cherry-picking process. This ensures only the selected crash fixes from closed PRs are efficiently merged into the target branch.

What are the limitations of using automated cherry-picking for release management?

Limitations of automated cherry-picking for release management include relying strictly on Git and GitHub CLI environments. Additionally, it targets specific fix categories like crash and test fixes, meaning broad code integration across unrelated features is not supported.