flow-next-export-context

Build RepoPrompt context and export it to a markdown file.

Updated Jan 15, 2026
One-click install
npx skills add https://github.com/tiendung/flow-next --skill flow-next-export-context-tiendung
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: flow-next-export-context
Source: https://github.com/tiendung/flow-next/tree/main/skills/flow-next-export-context
Command: npx skills add https://github.com/tiendung/flow-next --skill flow-next-export-context-tiendung

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Builds RepoPrompt context and exports it for external large-language-model reviews, enabling code and plan critiques without running in Ralph.

Core Features & Use Cases

  • Build RepoPrompt context for review of code or plans
  • Export the context to a markdown file suitable for external LLMs
  • Supports plan-export and impl-export workflows with the bundled flowctl

Quick Start

Run the bundled flowctl to generate a repo prompt export and view the resulting markdown file.

Frequently Asked Questions about flow-next-export-context

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

FAQPage Schema
How do I export code review context for an external LLM?

To export code review context for an external LLM, this skill builds RepoPrompt context and outputs a markdown file. It assembles repository state using the bundled flowctl script to enable external model critiques.

What is RepoPrompt context export used for?

RepoPrompt context export is used for generating shareable markdown files for large-language-model reviews. It enables external AI critiques of code and plans without executing the review process inside Ralph.

Can I use flowctl to generate a markdown file for plan reviews?

Yes, you can use the bundled flowctl to generate a markdown file for plan reviews. The skill supports both plan-export and impl-export workflows to assemble repository context for external models.

Do I need repository access to build RepoPrompt context?

Yes, you need repository state access to build RepoPrompt context. The skill requires reading the current repository files to assemble the necessary data and output the context markdown file.

How does exporting context differ from running an LLM review directly?

Exporting context generates a shareable markdown file for use outside the local environment, whereas running an LLM review directly processes the data internally. This approach supports external model preferences.

What are the limitations of using flowctl for context export?

A limitation of using flowctl for context export is the dependency on the bundled script and current repository state. It outputs a static markdown file, meaning subsequent code changes require regenerating the export.