Gptpro

GPTPro Export

Package a monorepo into clean, logically-split zip bundles for review by a powerful non-agentic model — GPT Pro on the ChatGPT web UI, or any chat model you upload files to.

That model has no shell, no live filesystem, and a bounded context. So we split by subsystem and strip node_modules, build output, binary assets, and secrets — giving it something it can actually navigate instead of a 400MB tarball it will choke on.

Run it with no config

bashCopy code
PROJECT_ROOT=/path/to/repo ./scripts/export.sh

With no bundles.conf, the script autodetects: one bundle per workspace package (apps/*, packages/*, services/*, libs/*), a schema-only db bundle from whatever migrations directory exists, and a docs bundle. A single-package repo gets one src bundle instead of the workspace walk.

That gets you a usable split on the first run. A hand-written config gets you a good one — the model navigates by asking "which bundle would this live in", so a split that matches your architecture is worth writing.

Configure

Bundles are defined in bundles.conf, which overrides autodetect entirely. Copy the example and edit:

bashCopy code
cp bundles.example.conf bundles.conf

Each line declares one bundle:

bashCopy code
define_bundle <name> "<description>" <source>...

Sources are dir:<path> or file:<path>[:<subdir>], relative to the repo root:

bashCopy code
define_bundle core "domain logic — the most important bundle for architecture review" \
  dir:packages/core

define_bundle db "schema architecture only — no rows, no seed data" \
  dir:supabase/migrations \
  file:supabase/config.toml:supabase \
  file:docs/DB_PLAN.md

define_bundle docs "architecture and convention context" \
  dir:docs dir:adrs file:README.md file:AGENTS.md

Run

bashCopy code
./scripts/export.sh

Overrides:

bashCopy code
PROJECT_ROOT=/path/to/repo \
OUTPUT_DIR=~/Desktop/review-bundles \
BUNDLE_PREFIX=myproject \
./scripts/export.sh

What gets excluded

Every bundle drops: .git, node_modules, .next, .turbo, dist, build, out, coverage, .vercel, *.tsbuildinfo, .env, .env.*, *.log, .DS_Store, and binary assets (images, video, fonts).

Tests are kept on purpose — they encode contracts and are some of the most useful review material in the repo.

Secret scan

After staging and before zipping, every bundle is scanned. Two tiers, because a one-tier scan on a real repo is all false positives and you end up passing ALLOW_SECRETS=1 every run — which is the same as having no scan:

• HARD — provider-issued credential shapes: private key headers, AKIA…, ghp_…, github_pat_…, xox…, AIza…, long sk-…/sk-ant-…, JWTs. A hit aborts the export, file and line printed. Override with ALLOW_SECRETS=1 only after reading every hit.
• SOFT — generic secret = "…" / password: "…" assignments. Printed for your eyes, never fatal.

Hits under test/, __tests__/, fixtures/, *.test.*, or carrying an obvious placeholder marker (FAKE, EXAMPLE, xxxxxxxx, env(…)) are demoted to SOFT — a secret-handling test suite is supposed to contain credential-shaped strings, and aborting on those trains you to ignore the guard.

Notes

• Split by subsystem, not by size. The model navigates by asking "which bundle would this live in" — a split that matches your architecture is worth more than evenly-sized zips.
• Database bundles should be architectural, not data. Ship the schema map and forward-only migrations so the model can see how the database is constructed; never ship rows or seed data.
• The output directory is wiped of prior *.zip on each run, so re-running gives a clean set with no stale bundles.
• Keep one bundle for docs/ADRs/conventions. Models reason much better about a codebase when they can read why it's shaped the way it is.

Pairs with gptpro-handoff — the workflow skill for authoring the prompt, receiving the report, and verifying findings before implementing.