InteractiveCommandVersion-control workflowsPull requests

/pr create

Pr Create/code/commands/interactive/pr-create

Create pull requests.

Options
4
Arguments
none
Examples
2
Industry
1 of 5 mapped

About

Supported options and rules: --base REF; --title TEXT; --draft; optional --body FILE.

Syntax

The canonical syntax string as recorded in the catalogue. It is authoritative — it is never reconstructed from the option and argument lists below.

/pr create

Subcommand of /pr

Arguments

None recordedThis command takes no positional arguments

Options

Defaults, allowed values, conflicts and scope come from the catalogue; blank fields mean the catalogue records nothing, not that the constraint is absent.

  • --base <string>stringOptional

    Choose the base Git reference used for comparison or creation.

  • --title <string>stringOptional

    Set the pull-request title.

  • --draftbooleanOptional

    Create the pull request as a draft. Default: False.

    Defaultfalse
  • --body <path>pathOptional

    Read pull-request body text from the specified file.

Examples

  • With options

    WITH OPTIONS
    /pr create --base main --draft

    Create pull requests.

  • Representative options

    WITH OPTIONS
    /pr create --base main --draft --title Fix pricing replay

    Shows representative optional controls available for this command.

Availability & requirements

Conditions under which the command is offered. Each row states its own kind of absence.

Conditions
git repository · pull request provider available
Requires repository
git
Requires authentication
UnknownThe catalogue records no auth requirement
Requires capabilities
pull request provider available
Platforms
UnknownAn empty platform list is not a claim of universal support

Relationships

Aliases

None recordedNo alias resolves to this command

Alternate surfaces

Not applicableThis command exists on one surface only

Related commands

None recordedNo related command is recorded

Industry comparison

1 of 5 products mapped

Command-level mappings against 5 audited products, each with its documentation source and capture date. No documented equivalent means the audit found nothing in that product’s official documentation — it is not a claim that the product lacks the capability.

Every canonical command was reviewed against all 5 products in one pass captured 2026-09-18. A product with no mapping is a reviewed finding of no documented equivalent, not an unreviewed pair.

Captured 2026-09-18 · 238 commands × 5 products

Open in Compare →