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

v1.0.0

À propos de ce Skill

Parfait pour les Agents d'intégration GitHub nécessitant une résolution de branche automatisée et une gestion de PR. Resume localise : Never trust plan docs or memory for branch names. It covers constraint-engine, cooperative-economics, did workflows. This AI agent skill supports Claude Code, Cursor, and Windsurf workflows.

Fonctionnalités

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
failing because the true head ref was feat/s22-compute-policy-config. That lookup took an extra

# 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: 8/11

This page remains useful for teams, 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
8/11
Quality Score
48
Canonical Locale
en
Detected Body Locale
en

Parfait pour les Agents d'intégration GitHub nécessitant une résolution de branche automatisée et une gestion de PR. Resume localise : Never trust plan docs or memory for branch names. It covers constraint-engine, cooperative-economics, did workflows. This AI agent skill supports Claude Code, Cursor, and Windsurf workflows.

Pourquoi utiliser cette compétence

Permet aux agents de résoudre les PR et les identités de branche à partir de GitHub, améliorant l'efficacité du flux de travail et évitant les erreurs, en exploitant l'intégration avec Claude Code, Cursor et Windsurf pour des expériences de codage de l'IA sans problème, et en utilisant des

Meilleur pour

Parfait pour les Agents d'intégration GitHub nécessitant une résolution de branche automatisée et une gestion de PR.

Cas d'utilisation exploitables for resolve-pr-branch

Automatiser la résolution de branche GitHub pour prévenir les erreurs
Résoudre les identités de PR et de branche avant le checkout ou le rebase
Améliorer les expériences de codage de l'IA avec l'intégration de Claude Code, Cursor et Windsurf

! Sécurité et Limitations

  • Nécessite une intégration avec GitHub
  • Limité aux systèmes de contrôle de version basés sur 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 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.

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

Parfait pour les Agents d'intégration GitHub nécessitant une résolution de branche automatisée et une gestion de PR. Resume localise : Never trust plan docs or memory for branch names. It covers constraint-engine, cooperative-economics, did workflows. This AI agent skill supports Claude Code, Cursor, and Windsurf workflows.

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: Automatiser la résolution de branche GitHub pour prévenir les erreurs, Résoudre les identités de PR et de branche avant le checkout ou le rebase, Améliorer les expériences de codage de l'IA avec l'intégration de Claude Code, Cursor et Windsurf.

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?

Nécessite une intégration avec GitHub. Limité aux systèmes de contrôle de version basés sur 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.

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

resolve-pr-branch

Resume localise : Never trust plan docs or memory for branch names. It covers constraint-engine, cooperative-economics, did workflows. This AI agent skill

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

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.

Compétences associées

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

Voir tout

openclaw-release-maintainer

Logo of openclaw
openclaw

Resume localise : 🦞 # OpenClaw Release Maintainer Use this skill for release and publish-time workflow. It covers ai, assistant, crustacean workflows. This AI agent skill supports Claude Code, Cursor, and Windsurf workflows.

widget-generator

Logo of f
f

Resume localise : Generate customizable widget plugins for the prompts.chat feed system # Widget Generator Skill This skill guides creation of widget plugins for prompts.chat . It covers ai, artificial-intelligence, awesome-list workflows. This AI agent skill supports Claude Code, Cursor, and

flags

Logo of vercel
vercel

Resume localise : The React Framework # Feature Flags Use this skill when adding or changing framework feature flags in Next.js internals. It covers blog, browser, compiler workflows. This AI agent skill supports Claude Code, Cursor, and Windsurf workflows.

138.4k
0
Navigateur

pr-review

Logo of pytorch
pytorch

Resume localise : Usage Modes No Argument If the user invokes /pr-review with no arguments, do not perform a review . It covers autograd, deep-learning, gpu workflows. This AI agent skill supports Claude Code, Cursor, and Windsurf workflows.

98.6k
0
Développeur