# Sq Pr

> Resolves and reports a pull request, or opens one from the current branch with a description assembled from the branch's own artifacts. Use when the user asks to show, check, or create a PR through squadron.

- Skill: `ecorkran/sq-pr` (Agent Skill)
- Install (CLI): `npx get-skill add ecorkran/sq-pr`
- Raw SKILL.md: https://api.skillmd.com/api/skills/ecorkran/sq-pr/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: ecorkran (https://skillmd.com/u/ecorkran)
- Updated: 2026-11-17
- Page: https://skillmd.com/skills/ecorkran/sq-pr

---


# sq pr

Run a pull-request command using squadron.

## Input parsing

The first word the user typed after `$sq-pr` is the subcommand. The remainder is passed to the CLI
unchanged — nothing is appended, substituted, or removed.

Valid subcommands: `show`, `create`

If the subcommand is missing or unrecognized, show the usage below and stop.

**Usage:**
```
$sq-pr show [TARGET] [FLAGS]     — resolve and report a pull request
$sq-pr create [FLAGS]            — open a pull request from the current branch
```

---

## Subcommand: show

Resolve a pull request, fetch its endpoints, and report the range.

Pass what the user typed after the leading `show` word directly to:

`sq pr show {remainder}`

An absent remainder is valid and passes through as absent — `sq pr show` with no target and no
flags resolves the current branch's pull request.

Optional arguments:
- Positional: pull request to show — a number, `owner/repo#number`, `repo#number`, a
  pull-request URL, or a branch. Omit to use the current branch.

Optional flags:
- `--cwd TEXT`: repository to resolve against
- `--json`: emit machine-readable JSON

Show the command's output.

---

## Subcommand: create

Open a pull request with a description assembled from the branch's own artifacts.

Pass what the user typed after the leading `create` word directly to:

`sq pr create {remainder}`

`sq pr create` writes to the host — it is the only thing that writes. This section carries four
rules for running it from a session:

- **`--dry-run` is offered, never substituted.** The flag is documented below; do not convert an
  operator's `create` into a dry run, and do not convert a `--dry-run` into a real create.
- **The command runs once.** On a non-zero exit, show the output and stop — do not retry. A
  create that failed after landing opens a second pull request if retried.
- **Printed remediation is shown, not executed.** A refusal for an unpushed branch prints the
  `git push` command to run. Show that line; do not run it — squadron does not push, and running
  it on the operator's behalf makes squadron push by proxy.
- **A refused base is not worked around.** Do not pass `--base` on the operator's behalf to get
  past a base-selection refusal.

Optional flags:
- `--base TEXT`: base branch
- `--dry-run`: print title and body without creating
- `--model TEXT`: model for the one-shot composer
- `--profile TEXT`: provider profile for the one-shot composer (default: `sdk`)
- `--cwd TEXT`: repository to resolve against
- `--title TEXT`: PR title, overriding the slice's name

Show the command's output.

## Waiting on the command

The `sq` commands this skill runs can take several minutes, print their own progress, and
finish on their own. Waiting costs nothing; checking on them does, because every check is a
full model turn.

- Run each command **once**. Never start it again because it seems slow.
- If the command is still running when the tool returns and you are given a session ID, wait
  on that session with `write_stdin`, empty `chars`, and `yield_time_ms` set to `300000`.
  Repeat exactly that until the command exits.
- Between waits, do nothing else: no status checks, no reading files, no commentary.

---

## If Codex blocks the command

If Codex rejects or blocks the `sq` command for sandbox or approval reasons — an approval
request that cannot be granted, a sandbox denial, or a network error such as "host
unreachable" from a command that needs a provider or GitHub — tell the user plainly that
this is **Codex's sandbox**, not the model provider and not squadron's configuration. Tell
them to run `sq install-commands --ide codex` from a terminal: it writes the Codex rules file
(`~/.codex/rules/squadron.rules`) that lets these `sq` commands run.
The "Codex sandbox approval rule" section of squadron's README has the details. Do not
suggest changing provider settings, API keys, or squadron config for this failure.

