pr

Creates GitHub pull requests and splits cross-layer branches into ordered stacked PRs.

74|11|Updated Jul 4, 2024
One-click install
npx skills add https://github.com/OpenSourceAGI/qwksearch-research-agent --skill pr-opensourceagi
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pr
Source: https://github.com/OpenSourceAGI/qwksearch-research-agent/tree/main/apps/qwk-in-lobe/.agents/skills/pr
Command: npx skills add https://github.com/OpenSourceAGI/qwksearch-research-agent --skill pr-opensourceagi

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Creating pull requests manually involves repetitive git and GitHub CLI steps, and cross-layer feature branches (database, server, clients) cannot merge safely as a single PR because callers depend on contracts that don't exist on the trunk yet. ## Core Features & Use Cases - Automated PR Creation: Gathers branch context, pushes changes, links related GitHub and Linear issues, and opens a PR against canary using the repository's PR template. - Stacked PR Splitting: Splits one cross-layer branch into ordered PRs so the server contract (TRPC, database schema) merges before its desktop, CLI, and UI callers. - Safety Guardrails: Uses backup branches, --force-with-lease, and explicit push targets to prevent accidental pushes to canary or lost commits. - Use Case: You finished a feature spanning packages/database, src/server, and apps/cli on one branch. Invoke this Skill to split it into a server PR and a stacked client PR, each closing only its own Linear issues. ## Quick Start Ask the assistant to create a PR for the current branch, or to split this branch into stacked PRs so the backend merges first.

Frequently Asked Questions about pr

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

FAQPage Schema
How do I create a GitHub pull request from the command line?

Use the GitHub CLI with `gh pr create --base canary` after pushing your branch. The Skill gathers branch context, fills the PR template, links related issues with keywords like `Fixes #123`, and opens the result in your browser.

How to split a large branch into stacked pull requests?

Back up the full commit, reset the lower-layer branch to the trunk, check out only the server and database files, then create a second branch based on it containing the client files. Open the client PR with `--base` set to the server branch so it cannot merge first.

When should I split a PR into stacked PRs?

Split when one branch changes multiple layers, such as a database schema, a TRPC server contract, and its desktop or CLI callers. If a PR merged alone would not build or behave correctly, it belongs in a later PR in the stack.

Why is force-with-lease used instead of force push?

`git push --force-with-lease` aborts if the remote branch moved since your last fetch, preventing you from overwriting someone else's commits. Plain `--force` overwrites the remote unconditionally, which risks losing work when rewriting branches.

Can I create a PR directly to the main branch?

No. This workflow targets `canary`, the development branch, and never creates PRs directly to `main`, which is reserved as the release branch. All PR content must also be written in English.