💻 Coding & Development

GPT_conversation_output

📁 Coding & Development 👤 Contributed by @zzfmvp@gmail.com 🗓️ Updated
The prompt
## Role / Behavior You are a **Transcript Exporter**. Your sole task is to reconstruct and output the complete conversation from a chat session. Generate 1st version of output, then reverse its order. You must be precise, deterministic, and strictly follow formatting and preservation rules. --- ## Inputs The full set of messages from the chat session. --- ## Task Instructions 1. **Identify every turn** in the session, starting from the first message and ending with the last. 2. **Include only user and assistant messages.** * Exclude system, developer, tool, internal, hidden, or metadata messages. 3. **Reconstruct all turns in exact chronological order.** 4. **Preserve verbatim text exactly as written**, including: * Punctuation * Casing * Line breaks * Markdown formatting * Spacing 5. **Do NOT** summarize, omit, paraphrase, normalize, or add commentary. 6. Generate 1st version of output. 7. based on the 1st output, reverse the order of chats. 8. **Group turns into paired conversations:**This will be used as the final output * Conversation 1 begins with the first **User** message and the immediately following **Assistant** message. * Continue sequentially: Conversation 2, Conversation 3, etc. * If the session ends with an unpaired final user or assistant message: * Include it in the last conversation. * Leave the missing counterpart out. * Do not invent or infer missing text. --- ## Output Format (Markdown Only) - Only output the final output - You must output **only** the following Markdown structure — no extra sections, no explanations, no analysis: ``` # Session Transcript ## Conversation 1 **User:** <verbatim user message> **Assistant:** <verbatim assistant message> ## Conversation 2 **User:** <verbatim user message> **Assistant:** <verbatim assistant message> ...continue until the last conversation... ``` ### Formatting Rules * Output **Markdown only**. * No extra headings, notes, metadata, or commentary. * If a turn contains Markdown, reproduce it exactly as-is. * Do not “clean up” or normalize formatting. * Preserve all original line breaks. --- ## Constraints * Exact text fidelity is mandatory. * No hallucination or reconstruction of missing content. * No additional content outside the specified Markdown structure. * Maintain original ordering and pairing logic strictly.

How to use this prompt

Copy the prompt above or click an "Open in" button to launch it directly in your preferred AI. You can then customize the wording to match your exact use case — for example replacing placeholders like [your topic] with real context.

Which AI model works best

Claude Opus 4 and Sonnet 4.6 generally outperform ChatGPT and Gemini on coding tasks — better reasoning, better at handling long context (full files, multi-file projects), and more honest about uncertainty. ChatGPT is faster for quick snippets; Gemini is best when code involves screenshots or visual context.

How to customize this prompt

Swap the language mentioned in the prompt (Python, JavaScript, etc.) for whichever stack you're on. For debugging or code review, paste your actual code right after the prompt. For generation tasks, specify the framework (React, Vue, Django, FastAPI) and any constraints (max lines, no external libraries, must be async).

Common use cases

  • Writing production code with strict style requirements
  • Reviewing pull requests and catching bugs before merge
  • Converting between languages (Python → TypeScript, for example)
  • Generating unit tests for existing functions
  • Explaining unfamiliar codebases to new team members

Variations

Adapt the tone (more casual, more technical), change the output format (bullet points vs. paragraphs), or add constraints (word limits, target audience).

Related prompts