Agent skill

flow-next-opencode-export-context

Export RepoPrompt context for external LLM review (ChatGPT, Claude web, etc.). Use when you want to review code or plans with an external model. Triggers on /flow-next:export-context.

View SKILL.md on GitHub Repository
Stars 34
Forks 0

Install this agent skill to your Project

npx add-skill https://github.com/gmickel/flow-next-opencode/tree/main/.opencode/skill/flow-next-opencode-export-context

SKILL.md

Export Context Mode

Build RepoPrompt context and export to a markdown file for use with external LLMs (ChatGPT Pro, Claude web, etc.).

Use case: When you want Carmack-level review but prefer to use an external model.

CRITICAL: flowctl is BUNDLED — NOT installed globally. which flowctl will fail (expected). Always use:

bash
ROOT="$(git rev-parse --show-toplevel)"
OPENCODE_DIR="$ROOT/.opencode"
FLOWCTL="$OPENCODE_DIR/bin/flowctl"
$FLOWCTL <command>

Input

Arguments: $ARGUMENTS Format: <type> <target> [focus areas]

Types:

  • plan <epic-id> - Export plan review context
  • impl - Export implementation review context (current branch)

Examples:

  • /flow-next:export-context plan fn-1 focus on security
  • /flow-next:export-context impl focus on the auth changes

Setup

bash
ROOT="$(git rev-parse --show-toplevel)"
OPENCODE_DIR="$ROOT/.opencode"
FLOWCTL="$OPENCODE_DIR/bin/flowctl"
REPO_ROOT="$(git rev-parse --show-toplevel 2>/dev/null || pwd)"

Workflow

Step 1: Determine Type

Parse arguments to determine if this is a plan or impl export.

Step 2: Gather Content

For plan export:

bash
$FLOWCTL show <epic-id> --json
$FLOWCTL cat <epic-id>

For impl export:

bash
git branch --show-current
git log main..HEAD --oneline 2>/dev/null || git log master..HEAD --oneline
git diff main..HEAD --name-only 2>/dev/null || git diff master..HEAD --name-only

Step 3: Setup RepoPrompt

bash
eval "$($FLOWCTL rp setup-review --repo-root "$REPO_ROOT" --summary "<summary based on type>")"

Step 4: Augment Selection

bash
$FLOWCTL rp select-get --window "$W" --tab "$T"

# Add relevant files
$FLOWCTL rp select-add --window "$W" --tab "$T" <files>

Step 5: Build Review Prompt

Get builder's handoff:

bash
$FLOWCTL rp prompt-get --window "$W" --tab "$T"

Build combined prompt with review criteria (same as plan-review or impl-review).

Set the prompt:

bash
cat > /tmp/export-prompt.md << 'EOF'
[COMBINED PROMPT WITH REVIEW CRITERIA]
EOF

$FLOWCTL rp prompt-set --window "$W" --tab "$T" --message-file /tmp/export-prompt.md

Step 6: Export

bash
OUTPUT_FILE=~/Desktop/review-export-$(date +%Y%m%d-%H%M%S).md
$FLOWCTL rp prompt-export --window "$W" --tab "$T" --out "$OUTPUT_FILE"
open "$OUTPUT_FILE"

Step 7: Inform User

Exported review context to: $OUTPUT_FILE

The file contains:
- Full file tree with selected files marked
- Code maps (signatures/structure)
- Complete file contents
- Review prompt with Carmack-level criteria

Paste into ChatGPT Pro, Claude web, or your preferred LLM.
After receiving feedback, return here to implement fixes.

Note

This skill is for manual external review only. It does not work with Ralph autonomous mode (no receipts, no status updates).

Recommended Agent Skills

Expand your agent's capabilities with these related and highly-rated skills.

gmickel/flow-next-opencode

flow-next-opencode-worktree-kit

Manage git worktrees (create/list/switch/cleanup) and copy .env files. Use for parallel feature work, isolated review, clean workspace, or when user mentions worktrees.

34 0
Explore
gmickel/flow-next-opencode

flow-next-opencode-setup

Local install of flowctl CLI and CLAUDE.md/AGENTS.md instructions. Use when user runs /flow-next:setup.

34 0
Explore
gmickel/flow-next-opencode

flow-next-opencode-sync

Manually trigger plan-sync to update downstream task specs after implementation drift. Use when code changes outpace specs.

34 0
Explore
gmickel/flow-next-opencode

flow-next-opencode-ralph-init

Scaffold repo-local Ralph autonomous harness under scripts/ralph/. Use when user runs /flow-next:ralph-init.

34 0
Explore
gmickel/flow-next-opencode

flow-next-opencode-plan

Create structured build plans from feature requests or Flow IDs. Use when planning features or designing implementation. Triggers on /flow-next:plan with text descriptions or Flow IDs (fn-1, fn-1.2).

34 0
Explore
gmickel/flow-next-opencode

flow-next-opencode-plan-review

Carmack-level plan review via RepoPrompt or OpenCode. Use when reviewing Flow epic specs or design docs. Triggers on /flow-next:plan-review.

34 0
Explore

Didn't find tool you were looking for?

Be as detailed as possible for better results