← Back to all workflows
Utility

Do you want to create a track changes Word document?

Generate a genuine, native Word document with Track Changes showing exactly what the AI changed in your document, ready for you to Accept or Reject.

Under the Hood

This is the actual text of the workflow

Inputs: This workflow requires two files: (1) the Original File (unmodified base document) and (2) the Updated File (the already-edited version containing the changes). If either file is missing, STOP AND ASK THE USER.

  1. Read Both Files: Read the original file and the updated file in full. Understand what the original currently says and how it's structured. Understand what changed in the updated file. Do NOT edit the original directly.

  2. Check/Recreate Tooling: Verify track_changes_exporter.py, track_changes_importer.py, track_changes_bold_postprocess.py exist. If not, recreate exactly using source at bottom.

  3. Generate Review DOCX: Run: python [track_changes_exporter.py](/scripts/track_changes_exporter) [original_file] [updated_name].[ext]. The script automatically generates [updated_name]_TC.docx (strip the original extension before appending _TC.docx to avoid stacking like contract.md_TC.docx). This creates native Word Track Changes via inline diffing.

    • MUST PRODUCE ACTUAL TRACKED CHANGES: Generates genuine redlines for Accept/Reject. Do not just export flat text. If the result lacks genuine tracked changes, you has FAILED and must retry with the proper exporter.
    • CRITICAL ANTI-LAZINESS WARNING: Use provided script. Custom/quick scripts (difflib.Differ inline) often fall back to blunt line block replacements, deleting whole paragraphs for one typo. The exporter does precise word-by-word diffing. Do not bypass.
    • ONLY text of the edited file. No titles, headers, descriptions, or conversational text. 3b. Apply Formatting: Run bold post-processor: python [track_changes_bold_postprocess.py](/scripts/track_changes_bold_postprocess) [updated_name]_TC.docx. Converts **bold** to Word formatting.

  4. Generate Reasoning Document: Create a markdown file named [updated_name]_TC_Reasoning.md in the same directory. Inside it, output a clean, vertical list (e.g., using bold headers like **Original Text:**, **Updated Text:**, and **Reasoning:**) detailing all substantive changes you made to the file and your logic behind them. DO NOT use a Markdown table, as they consistently fail to word-wrap long text blocks.

  5. If the user wants to make further changes to the track changes document: Sometimes the user will open the word document, edit it further using a second level of track changes, and then save that. They will tell you if that happens. If it does, rename current [updated_name].[ext] to [updated_name]_oldv{N}.[ext] (starting with v1 and incrementing N from the last version). Run python [track_changes_importer.py](/scripts/track_changes_importer) [updated_name]_TC.docx [updated_name].[ext].

  6. Done. The base filename always contains the current final version. The _oldvN files preserve the full version history. Cleanup any remaining scratch files.

The Output

When you run this workflow, the AI agents will generate the following folders and files:

  • [updated_name]_TC.docx - A native Word document containing your original text with all AI modifications appearing as Track Changes.

    • Example: contract_TC.docx

  • [updated_name]_TC_Reasoning.md - A vertical list detailing all substantive changes made to the file and the logic behind them.

    • Example: contract_TC_Reasoning.md

How to Set This Up

Option 1: The Easy Way (Automated)

Just point Antigravity to this webpage and ask it to figure it out for you. Antigravity can read this documentation, copy the workflow script, and automatically generate all the required skill files in the correct directories on your machine.

Option 2: The Hard Way (Manual Copy & Paste)

If Antigravity fails to set this up automatically, you will need to manually copy the scripts into your local directories:

  1. Copy the raw workflow script from the "Under the Hood" section above.
  2. Save it as C:\Users\[Your Name]\.gemini\antigravity\global_workflows\track_changes.md.
  3. You must also click every hyperlinked skill file and save its contents into your skills directory. You must do this for every single skill file linked in the workflow. For example, the legal_analysis_partner skill must be saved to C:\Users\[Your Name]\.gemini\antigravity\skills\legal_analysis_partner\SKILL.md.
  4. Once all files are saved, open Antigravity and type /track_changes in the chat to run it.

New to Antigravity? Read the Master Installation Guide first.