pr-loop-cloud-transport

Routes PR-loop skill operations through GitHub MCP tools when gh CLI is unavailable.

6|1|Updated Jul 11, 2026
One-click install
npx skills add https://github.com/jl-cmd/claude-dev-env --skill pr-loop-cloud-transport-jl-cmd
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: pr-loop-cloud-transport
Source: https://github.com/jl-cmd/claude-dev-env/tree/main/packages/claude-dev-env/.agents/skills-archived/pr-loop-cloud-transport
Command: npx skills add https://github.com/jl-cmd/claude-dev-env --skill pr-loop-cloud-transport-jl-cmd

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Cloud Claude Code sessions ship without a working gh CLI — the binary is missing, unauthenticated, or authenticated as an account that cannot act on the PR — so every gh step in PR-loop skills (pr-converge, autoconverge, bugteam, clean-room audit, pr-fix-protocol, copilot-review) fails. This Skill provides the setup and routing contract that substitutes GitHub MCP tools for every gh operation so those skills can run in cloud sessions. ## Core Features & Use Cases - Transport decision checks: Runs three ordered checks (command -v gh, gh auth status, and a push-permission probe via gh api repos/<owner>/<repo>) to decide between the local path and the cloud transport. - Six-step cloud setup workflow: Loads deferred MCP tool schemas, fixes missing origin/HEAD refs that break pre-push hooks, reads the live MCP identity via mcp__github__get_me, and keys review rules to it. - Operation substitution matrix: Maps every gh operation (PR reads, review threads, inline replies, Copilot review requests, draft toggles, CI logs) to its exact MCP tool path, with pagination rules and a scoped REST fallback. - Use Case: A cloud session running pr-converge cannot execute gh pr view or post reviews; this Skill routes those calls through mcp__github__pull_request_read and mcp__github__pull_request_review_write and self-checks posts that the gh-text hooks no longer gate. ## Quick Start Run the PR-loop cloud transport checks at the start of my session and route all GitHub operations through MCP tools if the gh CLI cannot act on the PR.

Frequently Asked Questions about pr-loop-cloud-transport

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

FAQPage Schema
How do I run PR-loop skills in a Claude Code cloud session without gh CLI?▼

Run the cloud transport workflow: load the GitHub MCP tool schemas with ToolSearch, fix origin/HEAD in each repo root, read the MCP identity with mcp__github__get_me, then route every gh operation through the substitution matrix mapping to mcp__github__* tools.

How to decide between local gh CLI and GitHub MCP transport?▼

Run three checks in order: command -v gh for the binary, gh auth status for an authenticated account, and gh api repos/<owner>/<repo> --jq .permissions.push for write access. Any failure routes the run to the cloud MCP transport.

Why do MCP tool calls fail with InputValidationError in cloud sessions?▼

MCP tool schemas are deferred, so a call before its schema loads fails with InputValidationError. Load schemas once per session with ToolSearch naming each fully prefixed mcp__github__* tool, then verify with mcp__github__get_me.

Why does git push fail with 'Not a valid object name origin/HEAD' in cloud clones?▼

Cloud clones do not set origin/HEAD, and the pre-push hook resolves its base ref from it. Run git -C <repo-root> remote set-head origin -a in every repo root the run touches, then push again without using --no-verify.

Can GitHub MCP tools replace all gh CLI operations for PR reviews?▼

Most operations map to MCP tools, including review threads, inline replies, and draft toggles, but custom GraphQL queries, Copilot quota reads, and second-reviewer account swaps have no cloud path. Claude-only slash commands also require a separate chain-spawn helper.

How do I check Copilot reviewer status without the gh quota API?▼

Treat Copilot quota as unknown and call mcp__github__request_copilot_review, then read status from what lands on the PR. A Copilot review on HEAD means it is up; an out-of-usage notice or no review within the poll budget means it is down.