Create PRs from a Fleetshift shift

Once Fleetshift has finished running a shift on a set of targets (the agent job completed successfully), you can open one pull request per completed target. Only targets whose job is complete are eligible for a PR.

Mutating action — explicit confirmation required. Do not call fleetshift:create-prs until the user has explicitly confirmed how many PRs will be opened and for which targets. Ask for a clear "yes" first.

Prerequisites

• The Portal CLI is authenticated: npx @spotify/portal-cli auth show. If it isn't, ask the user to run npx @spotify/portal-cli auth login. If auth list shows more than one Portal instance, confirm which one with the user and pass --instance <name> on every call.
• If a Portal MCP server is connected instead, the same actions are available as fleetshift_<action> tools (for example fleetshift_list-shifts). They take the same input, but have no --dry-run, so the confirmation steps below matter even more.
• Never pass --yes. It confirms actions marked destructive (stop-jobs, close-prs, delete-shift). Only the fleetshift-run-shift kill switch uses it, for stop-jobs.
• The shift has been run and at least one target reached a completed state (see the fleetshift-run-shift skill).

1. Confirm PRs can be opened (read-only)

Check the shift's status breakdown and the individual targets before creating anything:

# Aggregate: how many targets are jobComplete vs still running/failed
npx @spotify/portal-cli actions fleetshift:get-shift --input '{"shiftName":"<shift-name>"}' --json

# Only the completed targets (the ones PRs would be opened for)
npx @spotify/portal-cli actions fleetshift:get-shift-targets --input '{"shiftName":"<shift-name>","status":"jobComplete"}' --json

# If you have a job identifier from a prior run, you can confirm its status too
npx @spotify/portal-cli actions fleetshift:get-job-status --input '{"jobIdentifier":"<job-identifier>"}' --json

• Skip targets that are jobRunning or jobFailed. They aren't PR-eligible.
• If a target already has a prUrl, it is already covered; don't open a duplicate.

2. Confirm explicitly, then create (mutating)

Pass the eligible targets explicitly in targetIds, so only those get PRs. Validate the call with --dry-run first, which opens nothing:

npx @spotify/portal-cli actions fleetshift:create-prs --input '{"shiftName":"<shift-name>","targetIds":["component:default/my-service"]}' --dry-run --json

Present the exact number of PRs and the affected repositories to the user and get explicit confirmation. Then run the same command without --dry-run:

npx @spotify/portal-cli actions fleetshift:create-prs --input '{"shiftName":"<shift-name>","targetIds":["component:default/my-service"]}' --json

• Confirm the count with the user first (e.g. "This opens 12 PRs — proceed?").
• create-prs only opens PRs. It never closes, merges, or reverts PRs or branch changes.

3. Verify and report

Confirm each successfully created PR and report it:

npx @spotify/portal-cli actions fleetshift:get-shift-targets --input '{"shiftName":"<shift-name>","status":"jobComplete"}' --json

Link each opened PR (prUrl/prNumber). State clearly that the PRs are created but not merged, and that the user must review/merge them.

Boundaries

• No destructive actions. This skill never calls stop-jobs, close-prs, delete-shift, or any action that removes or reverts work.
• If a target is jobFailed and the user wants it fixed, point to the fleetshift-troubleshoot-shift skill (diagnosis) and fleetshift-run-shift (re-run) — both keep their own explicit confirmation requirement.