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
/plugin marketplace add gmickel/flow-next
/plugin install flow-next@flow-nextWhat 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-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/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/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?
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.