Skip to main content
skill CX Codex

flow-next-make-pr · gmickel — Claude Code skill for opening PRs

flow-next-make-pr is a Claude Code skill that builds a briefing from an aid artifact and opens or updates a PR through gh. It detects the spec from the branch and accepts options for draft state, base branch, and dry runs.

MIT ★ 730 updated 2026-10-29

Install into Claude Code · Plugin marketplace All methods and platforms ↓
/plugin marketplace add gmickel/flow-next
/plugin install flow-next@flow-next
Open on GitHub

What flow-next-make-pr does

The skill turns an aid artifact into a briefing: flowctl validates and stores the object, then renders the result. It identifies the spec from the current branch; when the branch has no spec, it follows the no-spec path in workflow.md. An executable flowctl and gh are required to create or update a PR.

Options control the PR state and base branch: --draft, --ready, --base, and --update. With --dry-run, it previews without repository writes, pushing, PR edits, or memory writes; --memory enables memory writes. The skill does not merge PRs. In autonomous mode, missing information causes an error, and evidence and requirement attribution must come from the export and its receipts.

What it helps with

  • render a briefing from an aid artifact
  • open a PR for the current branch
  • refresh an existing open PR
  • preview the proposed work without repository writes

Example prompts for the agent

  • Create a briefing from the aid artifact and open a PR for this branch.
  • Refresh the open PR for this spec as a draft.
  • Preview the PR changes without pushing or writing to the repository.

How to install flow-next-make-pr

1Plugin marketplace

/plugin marketplace add gmickel/flow-next
/plugin install flow-next@flow-next

This installs the whole flow-next plugin with all its skills

2Skills CLI (Vercel)

npx skills add gmickel/flow-next --skill flow-next-make-pr -a claude-code

3Manually: put the files in place

~/.claude/skills/flow-next-make-pr/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/flow-next-make-pr/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about flow-next-make-pr

How do I install flow-next-make-pr in Claude Code?

Add the marketplace with /plugin marketplace add gmickel/flow-next, then install the skill with /plugin install flow-next@flow-next.

What does flow-next-make-pr do?

It renders a briefing from an aid artifact, then uses gh to open or update a PR. It finds the spec from the branch and does not merge PRs.

What does flow-next-make-pr need to run?

It needs an executable flowctl in a supported location, gh, and an aid artifact. Creating a PR authorizes pushing the branch and opening the PR.

Source text

SKILL.md · MIT
---
name: flow-next-make-pr
description: Render a briefing from the aid artifact and open or update a PR via gh. Auto-detects the spec from the branch. Supports --draft, --ready, --base, --memory, --dry-run, --update, and mode:autonomous.
user-invocable: false
allowed-tools: AskUserQuestion, Read, Bash, Grep, Glob, Write, Edit, Task
---
# /flow-next:make-pr

The host authors one grounded aid object; flowctl validates, stores and renders the briefing. Read
[workflow.md](workflow.md), then its reached references. No extra model call or hand-assembled sections.
Invocation authorizes push and PR creation; `--dry-run` previews without repository writes, push, PR edits
or memory writes.

Read [working-rules.md](../../references/working-rules.md) first unless you already have this run; it holds for every step of this skill.

Define `FLOWCTL` from `${DROID_PLUGIN_ROOT:-${CLAUDE_PLUGIN_ROOT}}/scripts/flowctl`, then
`<plugin-root>/scripts/flowctl` (two levels above this SKILL.md), then `.flow/bin/flowctl`, choosing the first
executable. Never assume a global install. Parse `$ARGUMENTS`: the positional token is `SPEC_ID`; reject
unknown flags and missing base values. Carry these values between tool calls:

| Argument | Variable / effect |
| --- | --- |
| `--draft`, `--ready` | `DRAFT_FORCE=draft|ready`; default `auto`; last wins, note conflicts |
| `--base <ref>` or `--base=<ref>` | `BASE_REF`; default empty |
| `--memory` | `WRITE_MEMORY=1`; default 0 |
| `--dry-run` | `DRY_RUN=1`; default 0 |
| `--update` | `UPDATE_MODE=1`; default 0; refresh an existing open PR |
| `mode:autonomous` or `FLOW_AUTONOMOUS=1` | `AUTONOMOUS=1`; default 0 |

Keep this skill inline so `AskUserQuestion` remains available. Ask only for missing information, with a
recommended option; use a numbered prompt if the tool is unavailable. `NEED_INPUT:` means ask
outside Bash and rerun with the answer. Autonomous gaps hard-error instead. PRs open ready unless `--draft` or open items (rules in
create-and-finalize); a branch without a spec takes workflow.md's no-spec path. Never merge here. Evidence, paths and requirement attribution must be grounded in the export
and receipts, with unknowns explicit rather than invented.

© Gordon Mickel · MIT · gmickel/flow-next

Similar skills

All skills for Git and GitHub →

flow-next-make-pr by other authors comes first.

flow-next-make-pr Gordon Mickel flow-next-make-pr opens a pull request through gh, with the briefing body rendered by flowctl from the flow-next spec state. Fits repos where PRs are expected to follow a spec. CX Codex +1 ★ 730repo stars make-pr prathamdby make-pr publishes committed changes and creates or updates a pull request. It fits workflows that need branch checks and a post-operation state check. CX Codex +1 721installs make-repo-contribution official github The make-repo-contribution skill checks repository rules before issues, branches, commits, or pull requests, then guides the contribution workflow. CX Codex +1 11,073installs make-pr-easy-to-review cursor The make-pr-easy-to-review skill prepares pull requests for review by cleaning noisy history, refining the PR description, and adding reviewer guidance without changing code behavior. CX Codex +1 3,400installs pr-flow modelcontextprotocol pr-flow walks a task from issue to pull request and closes it after merge: branch, DCO signoff, pre-push gate, Copilot review. CX Codex +1 ★ 92,149repo stars git-flow-manager davila7 git-flow-manager — a Claude subagent that creates Git Flow branches, merges them, tags releases and opens pull requests. Useful when the branching scheme is strict but nobody follows it by hand. CX Codex 3,127installs printing-press-publish mvanhorn The printing-press-publish skill for Claude Code publishes a generated CLI from a local library to printing-press-library. It opens or updates the related pull request. CX Codex +1 7,200installs

From the same set70

The whole set →
flow-next-setup flow-next-setup links a repo to the flow-next plugin: adds versioned docs and config to CLAUDE.md or AGENTS.md. Other agents, such as Codex or Cursor, can then read the same instructions. CX Codex +1 ★ 730repo stars flow The flow command drives a task from idea or bug to ready PR. Works for unattended runs on a ready spec or step-by-step with stops before decisions. CX Codex +1 ★ 730repo stars flow-next-prose flow-next-prose — a skill for Claude and Codex that makes the agent read the prose contract in docs/prose.md before a long reply and draft under rules 1–10. CX Codex +1 ★ 730repo stars flow-next flow-next directs AI models to manage fn-N tasks using flowctl instead of markdown TODO lists. CX Codex +1 ★ 730repo stars flow-next-worktree-kit flow-next-worktree-kit is a Claude Code skill that creates, switches, and removes git worktrees and copies .env files between them. It supports parallel feature work without switching branches. CX Codex +1 ★ 730repo stars flow-next-land The flow-next-land skill handles feedback and CI checks for a named pull request, then squash-merges it when authorized and ready. Use it when asked to land a specific PR. CX Codex +1 ★ 730repo stars flow-next-make-pr flow-next-make-pr opens a pull request through gh, with the briefing body rendered by flowctl from the flow-next spec state. Fits repos where PRs are expected to follow a spec. CX Codex +1 ★ 730repo stars uninstall uninstall removes flow-next from your repository. It cleans docs markers and generates safe terminal commands for deleting project files. CX Codex +1 ★ 730repo stars

Project sponsors

Companies that keep this analytics open