release-check-out-pr — graphql release-check-out-pr, community, graphql, ide skills, http-client, websocket, Claude Code, Cursor, Windsurf

v1.0.0

About this Skill

Perfect for GitHub Integration Agents needing streamlined PR management capabilities. Check out a GitHub pull request for review in this repo, either in the current directory or in a new isolated worktree at ../yaak-worktrees/pr-<PR_NUMBER>. Use when asked to run or replace the old Cla

# Core Topics

mountain-loop mountain-loop
[17.9k]
[714]
Updated: 2/26/2026

Killer-Skills Review

Decision support comes first. Repository text comes second.

Reference-Only Page Review Score: 7/11

This page remains useful for operators, but Killer-Skills treats it as reference material instead of a primary organic landing page.

Original recommendation layer Concrete use-case guidance Explicit limitations and caution Locale and body language aligned
Review Score
7/11
Quality Score
30
Canonical Locale
en
Detected Body Locale
en

Perfect for GitHub Integration Agents needing streamlined PR management capabilities. Check out a GitHub pull request for review in this repo, either in the current directory or in a new isolated worktree at ../yaak-worktrees/pr-<PR_NUMBER>. Use when asked to run or replace the old Cla

Core Value

Empowers agents to seamlessly interact with GitHub PRs using the `gh` CLI, providing features like PR listing, metadata reading, and flexible checkout options via REST, GraphQL, WebSockets, Server Sent Events, and gRPC protocols.

Ideal Agent Persona

Perfect for GitHub Integration Agents needing streamlined PR management capabilities.

Capabilities Granted for release-check-out-pr

Automating PR checkout for streamlined development workflows
Debugging PR issues with isolated worktree checkout
Managing multiple PRs with efficient listing and selection

! Prerequisites & Limits

  • Requires `gh` CLI availability
  • Limited to GitHub PRs
  • Needs user input for PR selection and checkout options

Why this page is reference-only

  • - The underlying skill quality score is below the review floor.

Source Boundary

The section below is imported from the upstream repository and should be treated as secondary evidence. Use the Killer-Skills review above as the primary layer for fit, risk, and installation decisions.

Curated Collection Review

Reviewed In Curated Collections

This section shows how Killer-Skills has already collected, reviewed, and maintained this skill inside first-party curated paths. For operators and crawlers alike, this is a stronger signal than treating the upstream README as the primary story.

After The Review

Decide The Next Action Before You Keep Reading Repository Material

Killer-Skills should not stop at opening repository instructions. It should help you decide whether to install this skill, when to cross-check against trusted collections, and when to move into workflow rollout.

Labs Demo

Browser Sandbox Environment

⚡️ Ready to unleash?

Experience this Agent in a zero-setup browser environment powered by WebContainers. No installation required.

Boot Container Sandbox

FAQ & Installation Steps

These questions and steps mirror the structured data on this page for better search understanding.

? Frequently Asked Questions

What is release-check-out-pr?

Perfect for GitHub Integration Agents needing streamlined PR management capabilities. Check out a GitHub pull request for review in this repo, either in the current directory or in a new isolated worktree at ../yaak-worktrees/pr-<PR_NUMBER>. Use when asked to run or replace the old Cla

How do I install release-check-out-pr?

Run the command: npx killer-skills add mountain-loop/yaak/release-check-out-pr. It works with Cursor, Windsurf, VS Code, Claude Code, and 19+ other IDEs.

What are the use cases for release-check-out-pr?

Key use cases include: Automating PR checkout for streamlined development workflows, Debugging PR issues with isolated worktree checkout, Managing multiple PRs with efficient listing and selection.

Which IDEs are compatible with release-check-out-pr?

This skill is compatible with Cursor, Windsurf, VS Code, Trae, Claude Code, OpenClaw, Aider, Codex, OpenCode, Goose, Cline, Roo Code, Kiro, Augment Code, Continue, GitHub Copilot, Sourcegraph Cody, and Amazon Q Developer. Use the Killer-Skills CLI for universal one-command installation.

Are there any limitations for release-check-out-pr?

Requires `gh` CLI availability. Limited to GitHub PRs. Needs user input for PR selection and checkout options.

How To Install

  1. 1. Open your terminal

    Open the terminal or command line in your project directory.

  2. 2. Run the install command

    Run: npx killer-skills add mountain-loop/yaak/release-check-out-pr. The CLI will automatically detect your IDE or AI agent and configure the skill.

  3. 3. Start using the skill

    The skill is now active. Your AI agent can use release-check-out-pr immediately in the current project.

! Reference-Only Mode

This page remains useful for installation and reference, but Killer-Skills no longer treats it as a primary indexable landing page. Read the review above before relying on the upstream repository instructions.

Upstream Repository Material

The section below is imported from the upstream repository and should be treated as secondary evidence. Use the Killer-Skills review above as the primary layer for fit, risk, and installation decisions.

Upstream Source

release-check-out-pr

Install release-check-out-pr, an AI agent skill for AI agent workflows and automation. Works with Claude Code, Cursor, and Windsurf with one-command setup.

SKILL.md
Readonly
Upstream Repository Material
The section below is imported from the upstream repository and should be treated as secondary evidence. Use the Killer-Skills review above as the primary layer for fit, risk, and installation decisions.
Supporting Evidence

Check Out PR

Check out a PR by number and let the user choose between current-directory checkout and isolated worktree checkout.

Workflow

  1. Confirm gh CLI is available.
  2. If no PR number is provided, list open PRs (gh pr list) and ask the user to choose one.
  3. Read PR metadata:
    • gh pr view <PR_NUMBER> --json number,headRefName
  4. Ask the user to choose:
    • Option A: check out in the current directory
    • Option B: create a new worktree at ../yaak-worktrees/pr-<PR_NUMBER>

Option A: Current Directory

  1. Run:
    • gh pr checkout <PR_NUMBER>
  2. Report the checked-out branch.

Option B: New Worktree

  1. Use path:
    • ../yaak-worktrees/pr-<PR_NUMBER>
  2. Create the worktree with a timeout of at least 5 minutes because checkout hooks run bootstrap.
  3. In the new worktree, run:
    • gh pr checkout <PR_NUMBER>
  4. Report:
    • Worktree path
    • Assigned ports from .env.local if present
    • How to start work:
      • cd ../yaak-worktrees/pr-<PR_NUMBER>
      • npm run app-dev
    • How to remove when done:
      • git worktree remove ../yaak-worktrees/pr-<PR_NUMBER>

Error Handling

  • If PR does not exist, show a clear error.
  • If worktree already exists, ask whether to reuse it or remove/recreate it.
  • If gh is missing, instruct the user to install/authenticate it.

Related Skills

Looking for an alternative to release-check-out-pr or another community skill for your workflow? Explore these related open-source skills.

View All

openclaw-release-maintainer

Logo of openclaw
openclaw

Your own personal AI assistant. Any OS. Any Platform. The lobster way. 🦞

333.8k
0
AI

widget-generator

Logo of f
f

Generate customizable widget plugins for the prompts.chat feed system

149.6k
0
AI

flags

Logo of vercel
vercel

The React Framework

138.4k
0
Browser

pr-review

Logo of pytorch
pytorch

Tensors and Dynamic neural networks in Python with strong GPU acceleration

98.6k
0
Developer