flow-next-make-pr · gmickel, codex — Claude Code skill: open a PR from spec state
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.
MIT ★ 730 updated 2026-10-29
/plugin marketplace add gmickel/flow-next
/plugin install flow-next@flow-nextWhat flow-next-make-pr does
The skill opens a pull request with gh. The briefing body is built by flowctl, which checks the aid object, stores it, and renders the result from the spec state. There is no extra confirmation step: the call itself clears the push and the PR.
flowctl is looked up at ${CODEX_HOME:-$HOME/.codex}/scripts/flowctl, then in the plugin's scripts/ folder, then at .flow/bin/flowctl; the first executable wins. Nothing assumes a global install, so a repo missing all three has no way to run. The positional token is SPEC_ID. Flags: --draft and --ready, --base <ref>, --memory, --update, --dry-run. That last one previews the whole run and skips repo writes, pushes, and PR edits.
Missing details are asked for in plain text, as a numbered list ending with a write-your-own option. PRs come up ready for review; draft only with --draft or while items stay open. No merging happens here.
What it helps with
- open a PR whose body comes from the spec state
- preview a PR run without pushing or writing
- refresh an existing open PR after the spec changes
- open a draft PR while some items are still open
- write run memory alongside the PR
Example prompts for the agent
- Open a PR for spec
SPEC-12 - Make a draft PR for
SPEC-7based onmain - Update the open PR from the spec and write run memory
How to install flow-next-make-pr
1Plugin marketplace
/plugin marketplace add gmickel/flow-next/plugin install flow-next@flow-nextThis 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-code3Manually: put the files in place
~/.claude/skills/flow-next-make-pr/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/flow-next-make-pr/
1Skills CLI (Vercel)
npx skills add gmickel/flow-next --skill flow-next-make-pr -a codex2Manually: put the files in place
.agents/skills/flow-next-make-pr/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add gmickel/flow-next --skill flow-next-make-pr -a cursor2Manually: put the files in place
.cursor/skills/flow-next-make-pr/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install gmickel/flow-next plugins/flow-next/codex/skills/flow-next-make-pr2Manually: put the files in place
.github/skills/flow-next-make-pr/SKILL.md1Skills CLI (Vercel)
npx skills add gmickel/flow-next --skill flow-next-make-pr -a gemini-cli2Platform CLI
gemini skills install https://github.com/gmickel/flow-next --path plugins/flow-next/codex/skills/flow-next-make-prManually: put the files in place
.devin/skills/flow-next-make-pr/SKILL.mdThe legacy .windsurf/skills/ path still works
Claude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
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?
Through the plugin marketplace: run /plugin marketplace add gmickel/flow-next, then /plugin install flow-next@flow-next. The skill ships with the flow-next plugin.
What does flow-next-make-pr do?
It opens a pull request with gh, and flowctl renders the briefing body from the spec state. Calling the skill is also the go-ahead for the push and the PR.
Can I use it in Claude Code?
Yes, install it there with npx skills add gmickel/flow-next --skill flow-next-make-pr -a codex.
Source text
SKILL.md · MIT
---
name: flow-next-make-pr
description: Open a PR with a cognitive-aid body rendered from flow-next spec state via gh. Use whenever asked to make or open a PR in a flow-next repo.
user-invocable: false
allowed-tools: 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 `${CODEX_HOME:-$HOME/.codex}/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 prompt turns:
| 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 |
**Ask the user via plain text.** Render the options below as a numbered list `1.` … `N.`, followed by a final option `N+1. Other — type your own answer`. Print the question, then the numbered list, then **stop and wait for the user's next message before continuing**. Parse the reply as: a bare number `1`–`N+1` → that option; the literal text of an option label → that option; free text after `Other` → custom answer.
Keep this skill inline so `plain-text numbered prompt` 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.