flow-next-export-context

Export RepoPrompt context to a consolidated markdown file for external LLM review.

Updated Jan 15, 2026

Search Tags:#automation #code-review #export #repo #flowctl #llm-review

Ready to run

npx skills add https://github.com/raydocs/inktale --skill flow-next-export-context-raydocs

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: flow-next-export-context
Source: https://github.com/raydocs/inktale/tree/main/plugins/flow-next/skills/flow-next-export-context
Command: npx skills add https://github.com/raydocs/inktale --skill flow-next-export-context-raydocs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Build RepoPrompt context and export to a markdown file for use with external LLMs (ChatGPT Pro, Claude web, etc.). This enables comprehensive external review of code, plans, and repository changes by an AI model.

Core Features & Use Cases

Build a cohesive RepoPrompt context from repository metadata, diffs, and plan details for external review.
Export a ready-to-share markdown document that can be fed into external LLMs (ChatGPT, Claude) for critique or validation.
Support both plan export (plan <epic-id>) and implementation export (impl) workflows to review different aspects of the repo.

Quick Start

Run the export-context workflow for your target epic or current branch to generate a review-ready markdown document.

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 repository context to a markdown file for external LLM review?▼

Export repository context to a markdown file for external LLM review by running the export-context workflow, which gathers repository metadata, diffs, and plan details into a consolidated document. This output is ready to share with models like ChatGPT or Claude.

Can I use this workflow to export both plan details and implementation diffs from my repo?▼

You can export both plan details and implementation diffs from your repo using the plan and impl workflows. The plan export targets specific epic IDs, while the implementation export captures current branch changes for external validation.

Does exporting RepoPrompt context require FlowCTL and a connected repository?▼

Exporting RepoPrompt context requires FlowCTL and repository context to function. The scripted workflow depends on FlowCTL to gather content, set up prompts, and generate the final consolidated markdown file for external models.

What is the best way to prepare my codebase changes for critique by an external AI model?▼

The best way to prepare codebase changes for critique by an external AI model is building a cohesive RepoPrompt context. This consolidates metadata and diffs into a single markdown document, providing comprehensive external review of your repository.

Why does my external LLM review fail when I paste raw repository diffs without context?▼

External LLM reviews often fail with raw diffs because they lack repository metadata and plan context. Exporting a consolidated markdown file with full RepoPrompt context provides the necessary structure for models like Claude to validate code accurately.

When do I need to generate a plan export versus an implementation export for external review?▼

Generate a plan export when you need to review epic-level architecture and strategy, and use an implementation export to review current branch code changes. Both workflows produce markdown files tailored for external LLM critique and validation.