flow-next-make-pr

Generates structured PR bodies from flow-next spec state and creates pull requests via gh.

692|55|Updated Dec 26, 2025
One-click install
npx skills add https://github.com/gmickel/gmickel-claude-marketplace --skill flow-next-make-pr
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: flow-next-make-pr
Source: https://github.com/gmickel/gmickel-claude-marketplace/tree/main/plugins/flow-next/codex/skills/flow-next-make-pr
Command: npx skills add https://github.com/gmickel/gmickel-claude-marketplace --skill flow-next-make-pr

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Reviewers receive large agent-generated diffs with no signal on where to focus. This Skill assembles a reviewable PR body from flow-next spec state — R-ID coverage, task evidence commits, decisions, deferred findings, and the git diff — so a human can decide where to look before reading code.

Core Features & Use Cases

  • Cognitive-aid PR body: Aggregates spec, tasks, memory, glossary, strategy, and diff data via flowctl spec export-cognitive-aid into a structured body with TL;DR, R-ID coverage table, risk-ranked review plan, and open items.
  • Mermaid structural diagrams: Emits validated mermaid diagrams (or diff-fenced sketches) for cross-module changes, with hard caps and a pre-emission checklist to avoid silent rendering failures.
  • Autonomous PR creation: Pushes the branch and runs gh pr create with a retry loop for GitHub eventual-consistency errors, smart draft/ready defaults, --dry-run preview, and optional tracker (Linear/GitHub/GitLab/Jira) issue linkage.
  • Use Case: After finishing a flow-next spec implementation, run the skill to open a draft PR whose body tells reviewers exactly which files must be reviewed, which requirements are evidenced, and which items remain open.

Quick Start

Ask the agent to open a PR for the current flow-next spec, optionally passing flags like --dry-run to preview the body or --base to override the target branch.

Frequently Asked Questions about flow-next-make-pr

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create a PR from a flow-next spec?

Invoke the make-pr skill with an optional spec id; it resolves the spec from the branch, exports the cognitive-aid payload via flowctl, renders the body, pushes the branch, and runs gh pr create. Use --dry-run to print the body without creating anything.

How do I preview the PR body without opening a pull request?

Pass the --dry-run flag. The skill renders the full body to stdout and exits before any git push or gh pr create call, so you can inspect it or pipe it to a clipboard tool.

Does the skill work without the GitHub CLI installed?

No. The gh CLI must be installed and authenticated; the pre-flight phase checks this and prints install or gh auth login instructions, then exits. There is no manual git push fallback for PR creation.

When does the PR open as a draft versus ready for review?

The PR opens as a draft when open items exist, under Ralph or autonomous mode, or with --draft. It opens ready only when there are no open items or --ready is forced interactively; --ready is ignored under autonomous modes.

Why did the mermaid diagram in my PR not render?

Mermaid silently fails on reserved words, unquoted special characters, emoji, or subgraph/node name collisions. The skill validates each diagram against a pre-emission checklist; you can also skip diagrams entirely with --no-mermaid.

Can the PR body link to a Linear or Jira issue?

Yes. When a tracker bridge is active, the skill appends a non-closing reference line (Ref/Refs) to the body before creation so Linear, GitHub, or GitLab auto-link the PR. Jira linking happens via a remote link on the issue instead.