skills.rest
maxbeaudoin
maxbeaudoinCOMMUNITY
Explore all skills by this author →
GitHub

open-pr

Push the current branch, open a GitHub PR, wait for CI, and squash-merge into main.

Updated Aug 23, 2026
Search Tags:#pull request#workflow automation#github#linear#squash merge#ci checks#branch workflow
One-click install
npx skills add https://github.com/maxbeaudoin/productflash --skill open-pr-maxbeaudoin
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: open-pr
Source: https://github.com/maxbeaudoin/productflash/tree/main/.claude/skills/open-pr
Command: npx skills add https://github.com/maxbeaudoin/productflash --skill open-pr-maxbeaudoin

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Open PRs, verify CI results, and keep GitHub and Linear issue states in sync without manual coordination or forgotten steps.

Core Features & Use Cases

  • PR Creation from Current Branch: Pushes the current branch, opens a GitHub PR, and creates a traceable PR body that closes or references the Linear issue.
  • Automated CI Wait with Failure Recovery: Polls PR checks until completion, exits with a failing status on CI failure, and guides you to fix via a new commit and re-run the wait.
  • Safety-Gated Squash Merge: Waits for explicit user confirmation before squash-merging into main, then fast-forwards local main.
  • Linear State Progression: Moves the issue to In Review immediately after PR creation and to Done after merge.

Quick Start

Ask: open the current branch as a PR, wait for CI, then squash-merge into main and mark the related Linear issue as Done.

Frequently Asked Questions about open-pr

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

FAQPage Schema
How do I automate pull request creation and Linear issue state updates?▼

Automating pull request creation and Linear issue updates involves pushing your branch, opening a GitHub PR, and transitioning the linked Linear issue to In Review and Done. This workflow requires deriving the Linear ID from the branch slug and using the workspace MCP Linear server.

How do I wait for CI checks to pass before merging a GitHub pull request?▼

Waiting for CI checks before merging involves polling PR checks via GitHub CLI exit codes until completion. If CI fails, the process exits with a failing status and guides you to fix the issue via a new commit and re-run the wait.

Can I squash merge a feature branch into main with explicit confirmation?▼

Squash merging a feature branch into main with explicit confirmation is supported by waiting for user approval before merging. After confirmation, it squash-merges into main and fast-forwards your local main branch.

What is needed to sync GitHub pull requests with Linear issue states?▼

Syncing GitHub pull requests with Linear issue states requires a feature-branch workflow where the Linear ID is derived from the branch slug. It also requires a clean working tree validation and the workspace MCP Linear server to transition states.

What happens if CI checks fail when automating a branch merge?▼

If CI checks fail during an automated branch merge, the process exits with a failing status. It then guides you to fix the failure by pushing a new commit and re-running the CI wait cycle.

Does this workflow require a clean git working tree before opening a PR?▼

Yes, opening a PR with this workflow requires clean working tree validation before proceeding. This ensures no uncommitted changes interfere with pushing the branch and automating the pull request creation.

Related Skills

Explore More Software Engineering Skills→
emiljuchnikowskiemiljuchnikowski

push

Automate Git pushes, Linear status updates, and pull request creation.

Community
Advanced
Clawdi-AIClawdi-AI
4

merge-pr

Merge GitHub pull requests via squash after validating checks and branch status.

Official
Advanced
zengbaochengzengbaocheng

github-pr-workflow

Automate GitHub PR lifecycle from branch creation through merge.

Community
Advanced
cookeyholdercookeyholder

squash-pr

Squash and merge a GitHub pull request into main after validating review feedback.

Community
Advanced