resolve-pr-branch — constraint-engine resolve-pr-branch, community, constraint-engine, ide skills, cooperative-economics, gossip-protocol, governance, mutual-credit, trust-graph, Claude Code, Cursor

v1.0.0

このスキルについて

GitHubのブランチ解析とPR管理の自動化が必要なGitHub統合エージェントに最適です。 Resolve PR↔branch identity from GitHub. Never trust plan docs or memory for branch names.

# Core Topics

InterCooperative-Network InterCooperative-Network
[5]
[0]
Updated: 3/22/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
Review Score
7/11
Quality Score
48
Canonical Locale
en
Detected Body Locale
en

GitHubのブランチ解析とPR管理の自動化が必要なGitHub統合エージェントに最適です。 Resolve PR↔branch identity from GitHub. Never trust plan docs or memory for branch names.

このスキルを使用する理由

エージェントがGitHubからPRとブランチIDを解決する能力を提供し、ワークフローの効率を高め、エラーを回避し、Claude Code、Cursor、Windsurfとの統合を利用してシームレスなAIコーディング体験を提供し、git checkoutやrebaseなどのプロトコルを利用します。

おすすめ

GitHubのブランチ解析とPR管理の自動化が必要なGitHub統合エージェントに最適です。

実現可能なユースケース for resolve-pr-branch

エラーを防ぐためにGitHubのブランチ解析を自動化する
チェックアウトまたはリベース前にPRとブランチIDを解決する
Claude Code、Cursor、Windsurfとの統合を利用してAIコーディング体験を強化する

! セキュリティと制限

  • GitHubの統合が必要
  • gitベースのバージョン管理システムに限定される

Why this page is reference-only

  • - Current locale does not satisfy the locale-governance contract.
  • - The underlying skill quality score is below the review floor.

Source Boundary

The section below is supporting source material from the upstream repository. Use the Killer-Skills review above as the primary decision layer.

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 resolve-pr-branch?

GitHubのブランチ解析とPR管理の自動化が必要なGitHub統合エージェントに最適です。 Resolve PR↔branch identity from GitHub. Never trust plan docs or memory for branch names.

How do I install resolve-pr-branch?

Run the command: npx killer-skills add InterCooperative-Network/icn/resolve-pr-branch. It works with Cursor, Windsurf, VS Code, Claude Code, and 19+ other IDEs.

What are the use cases for resolve-pr-branch?

Key use cases include: エラーを防ぐためにGitHubのブランチ解析を自動化する, チェックアウトまたはリベース前にPRとブランチIDを解決する, Claude Code、Cursor、Windsurfとの統合を利用してAIコーディング体験を強化する.

Which IDEs are compatible with resolve-pr-branch?

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 resolve-pr-branch?

GitHubの統合が必要. gitベースのバージョン管理システムに限定される.

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 InterCooperative-Network/icn/resolve-pr-branch. 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 resolve-pr-branch 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.

Imported Repository Instructions

The section below is supporting source material from the upstream repository. Use the Killer-Skills review above as the primary decision layer.

Supporting Evidence

resolve-pr-branch

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

SKILL.md
Readonly
Imported Repository Instructions
The section below is supporting source material from the upstream repository. Use the Killer-Skills review above as the primary decision layer.
Supporting Evidence

Resolve PR and branch identity from GitHub as the authoritative source. Use this before any checkout, rebase, force-push, or when a plan references a branch by name.

The Problem This Solves

Branch names in plans, notes, and memory drift. The transcript showed a git checkout feat/s22-compute-config failing because the true head ref was feat/s22-compute-policy-config. That lookup took an extra round-trip to recover. This skill makes the lookup the first step, not a recovery.

Steps

  1. Determine lookup direction from $ARGUMENTS:

    • If argument looks like a number → PR lookup
    • If argument looks like a branch name → branch lookup
    • If empty → show all open PRs with their head branches
  2. PR → head branch:

    bash
    1gh pr view <N> --json number,title,headRefName,baseRefName,state \ 2 --jq '{pr: .number, title: .title, head: .headRefName, base: .baseRefName, state: .state}'
  3. Branch → PR:

    bash
    1gh pr list --json number,title,headRefName,state \ 2 --jq '.[] | select(.headRefName == "<branch>") | {pr: .number, title: .title, state: .state}'
  4. Check local branch existence:

    bash
    1git branch --list <branch> # local 2git ls-remote --heads origin <branch> | grep -q . && echo "exists remotely"
  5. Fetch if missing locally but present remotely:

    bash
    1git fetch origin <branch>
  6. Detect stacked PRs (base ≠ main):

    bash
    1gh pr list --json number,headRefName,baseRefName \ 2 --jq '.[] | select(.baseRefName != "main") | "PR #\(.number) \(.headRefName) → \(.baseRefName)"'

Output format

PR #1391 · feat/s22-compute-policy-config → main  [OPEN]
  local branch: present
  remote:       present
  stacked:      no

Guardrails

  • Never proceed with a branch name that hasn't been confirmed against GitHub.
  • When a local checkout fails with "pathspec did not match", immediately run this skill instead of trying other branch name guesses.
  • Treat stacked PRs (base ≠ main) as requiring ordered integration.

ICN-specific notes

  • Sprint plan docs (ops/state/sprint/current.json) store branch names that can drift between plan-time and execution-time. Always verify against gh pr view.
  • Worktrees in icn-wt/ hold their own branch refs; a branch that appears absent may just be checked out in a worktree.

関連スキル

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

すべて表示

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

カスタマイズ可能なウィジェットプラグインをprompts.chatのフィードシステム用に生成する

149.6k
0
AI

flags

Logo of vercel
vercel

React フレームワーク

138.4k
0
ブラウザ

pr-review

Logo of pytorch
pytorch

Pythonにおけるテンソルと動的ニューラルネットワーク(強力なGPUアクセラレーション)

98.6k
0
開発者