Home / How it works
Guide

How it
works.

A practical walkthrough — load your ZIP, run a patch through the pipeline, use Diag Export to collaborate with your AI, and download a clean change set for UAT.

🚀 Beta is live at repopatch-api.onrender.com — anonymous sessions are free and need no signup. Microsoft Authenticator MFA is supported for longer sessions you can return to.
01 — Load your ZIP workspace ▾

Start by importing your project. RepoPatch creates an isolated workspace from your ZIP so nothing touches your local files until you're ready.

📦 Prepare a ZIP of your project folder. It doesn't need to be the whole repo — just the files you're working on is fine.
  1. 1
    Open RepoPatch Studio. You'll get an anonymous session — the countdown timer shows how long it lasts.
  2. 2
    Drag your project ZIP onto the import area, or click to browse and select it.
  3. 3
    The workspace loads and shows version v1.0 in the status bar. Your files are ready.
  4. 4
    Use the Summary tab to browse your workspace file list and confirm everything loaded.
  5. 5
    To start fresh at any time, just import a new ZIP — the workspace resets atomically and version jumps to v2.0.
💡 Nothing is stored long-term on the free tier. Anonymous workspaces are wiped automatically — so your code stays yours. Pro accounts get persistent workspaces that survive deploys.
02 — Run your patch through the pipeline ▾

Once your workspace is loaded, you feed in the AI's response and walk it through four pipeline stages before anything gets written.

🤖 Use the Diag Export button in the Summary tab to produce a single-file snapshot of your workspace to share with your AI model. Paste it in, describe what you want changed, and copy the patchset response back.
  1. 1
    Load: Paste your patchset into the Load tab (or drop the file). RepoPatch parses it and shows how many PATCH blocks were found.
  2. 2
    Conform: Click Conform. The Conform tab has four subtabs — Convert, Run, Issues, and Code Quality. Review any warnings — then click "I've reviewed these warnings — proceed" if you're happy.
  3. 3
    Validate: Click Validate. Every anchor in the patch is matched against your actual workspace files. If any anchor doesn't match, you'll see a line-by-line comparison showing exactly what's different.
  4. 4
    Apply: Once Validate passes, Apply becomes available. Click it to write the changes. Your workspace version increments (e.g. v1.0 → v1.1).
  5. 5
    After Apply, choose Record Success to keep the result, or Revert Failed Release to roll back. Pro accounts restore file contents from snapshot; free accounts roll back stage state only.
🛡️ Pro accounts see additional Code Quality tiles for governance: permission elevation (ModifyAllData, ViewAllData, AuthorApex), hardcoded Salesforce IDs, SOQL in loops, weak crypto, plaintext HTTP, and other smells the patch is introducing.
03 — Use Diag Export to talk to your AI model ▾

Diag Export is the bridge between RepoPatch and your AI. It packages your workspace into one clean file — with all the context the AI needs to produce a valid patchset in return.

📤 The export embeds the Patch Language spec automatically, so the AI already knows the rules. You just describe what you want changed.
  1. 1
    In the Summary tab, click Diag Export. A .txt file downloads containing your workspace snapshot.
  2. 2
    Open your AI model (Claude, GPT-4, Gemini, or any other). Upload or paste the export file.
  3. 3
    Describe the changes you want: new features, bug fixes, refactors — in plain language. The AI will respond with a PATCHSET.
  4. 4
    Copy the PATCHSET from the AI's response and paste it into RepoPatch's Load tab, then run it through the pipeline as in Step 2.
  5. 5
    If the AI's patch fails Validate, copy the diagnostic output and ask the AI to fix its anchors. Repeat until it passes.
💡 You can run multiple rounds — apply a patch, export again with the updated workspace, ask for more changes. Each round builds on the last.
04 — Download your change set and apply it for UAT ▾

Once you're happy with the applied changes, use Download Change Set to get only the files that changed — ready to drop straight into your UAT environment.

📥 The change set ZIP contains only the modified files from your last Apply, not the full workspace. It's designed for easy UAT deployment — copy the files over and test.
  1. 1
    After a successful Apply, go to the Summary tab and click Download Change Set.
  2. 2
    A ZIP downloads containing only the files that were modified or created by the patch. Open it to review the file list.
  3. 3
    Copy the changed files into your UAT environment (branch, staging server, or test folder) and run your tests.
  4. 4
    If UAT passes: go back to RepoPatch, click Record Success, and the version is locked in your history with a ✓.
  5. 5
    If UAT fails: click Revert Failed Release in RepoPatch to roll back to the previous version, then iterate — adjust your instructions to the AI and rerun the pipeline.
💡 You can also use Export Full Workspace at any time to download the complete updated project as a ZIP — useful for committing back to your repo when you're done with a sprint. Pro accounts can download any historical version from the picklist.

Ready to try it yourself?

Start a free anonymous session, import a ZIP, and run your first patch in minutes. No install required.

⚡ Try the Beta Version now See the full pipeline →