pr-base-scope

Set or unset the per-session PR target branch in local git config.

Updated Apr 17, 2026
One-click install
npx skills add https://github.com/smallorbit/smallorbit-plugins --skill pr-base-scope
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pr-base-scope
Source: https://github.com/smallorbit/smallorbit-plugins/tree/main/plugins/flowkit/skills/pr-base-scope
Command: npx skills add https://github.com/smallorbit/smallorbit-plugins --skill pr-base-scope

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Set or unset the claude.flowkit.prBase git config key to scope the PR target branch for a session. The key is local to the repository and controls where PRs point during ship and swarm flows. The legacy key claude.prBase is still read as a fallback for backward compatibility, but is never written. When read, it emits a one-line deprecation notice pointing at the migration commands.

Core Features & Use Cases

  • Pin the PR target branch for the current session with claude.flowkit.prBase.
  • Fall back to claude.prBase for backward compatibility (read-only) and default to develop if neither is set.
  • Used by /ship and /swarm loop mode to ensure PRs are scoped to the correct branch, and by /open-pr to determine the base.

Quick Start

Set the PR base for the current session to a target branch using git config claude.flowkit.prBase <branch>.

Frequently Asked Questions about pr-base-scope

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

FAQPage Schema
How do I set the PR target branch for a git session?

Pin the PR target branch for a session using git config claude.flowkit.prBase <branch>, which scopes pull request targeting locally to the current repository and session.

What happens if the legacy claude.prBase git config key is set?

The legacy claude.prBase git config key is read as a read-only fallback for backward compatibility and emits a deprecation notice, but new writes always target the claude.flowkit.prBase key instead.

What is the default PR base branch when no git config key is set?

The default PR base branch is develop, used when neither the claude.flowkit.prBase key nor the legacy claude.prBase fallback is configured in the local git repository.

Can I scope pull request targets for the /ship and /swarm flows?

Yes, you can scope pull request targets for the /ship, /swarm loop, and /open-pr flows by setting the claude.flowkit.prBase git config key to control the session's PR base branch.

How do I unset or remove a pinned PR base branch from git config?

Unset the per-session PR target branch by removing the claude.flowkit.prBase git config key, which allows the system to fall back to the legacy key or the built-in develop default.