What problem does it solve? Migrating ChatGPT project threads into a repository often loses regenerated branches, attachments, and provenance, making it impossible to prove what was captured or to safely publish distilled material. This Skill enforces a lossless capture-first workflow that preserves raw exports, normalizes every conversation node, and reconciles threads before any artifact is committed. ## Core Features & Use Cases - Lossless source preservation: Archives the original export ZIP outside Git with SHA-256 hashes, keeping raw evidence separate from public-safe artifacts. - Branch-complete normalization: Parses every node in the conversation mapping object, including regenerated alternatives and non-current branches, rather than only the visible current_node path. - Reconciliation and exception tracking: Matches UI-inventoried threads to export records by conversation ID and keeps unmatched threads, branches, and assets as open exceptions until resolved. - Use Case: You have a 200-thread ChatGPT project to fold into your repo. Use this Skill to inventory every thread, hash the export, normalize all mapping nodes, recover unmatched threads via browser capture, and route only reviewed, public-safe distillations into committed documentation. ## Quick Start Ask the agent to capture and migrate your ChatGPT project into the repository using the okhp3-chatgpt-project-migration workflow, starting with a project capture manifest.
