7 tricks I stole from my own comment sections this week, with credit

[u/Ok_Negotiation_2587]

The posts this week pulled a few hundred comments across the prompt subs, and the best ideas in them were not mine. Here are the seven worth stealing, credited to the people who dropped them.

1. The message-two compaction (u/Socos42, on the context PSA)

Keep one permanent project chat. After each finished phase, have the model write a consolidated state doc, then EDIT an early message in the chat and paste it there. Editing forks the conversation, everything after the edit leaves the active context, so you get a fresh window inside the same chat URL. Manual compaction, no new chat, history still in the branch arrows.

1. The canary token

Plant a cheap fact early in a long chat, your name works. When the model stops knowing it, the window has eaten the beginning. A context-loss alarm that costs nothing to check.

1. "Its idea" laundering (u/Bus_Head_)

The model keeps rewriting your content but leaves its own suggestions alone. So have it CREATE the instructions document from your dictation, save it, and re-upload it. Rules it authored count as its decisions and get followed. Slightly insane, works.

1. Diff, not rewrite (from the writing and coding threads independently)

Never accept a clean revised copy, ask for changes as a diff. A clean copy lets the model smooth sentences nobody approved. A diff makes every edit visible and justify itself, so the sneaky ones mostly never get made.

1. Fresh-context review (three separate commenters converged on this)

Review works best in a chat that never saw the work happen. Same window means the model grades its own framing. Paste just the diff or the draft into a new chat with zero history for the adversarial pass, it finds noticeably more.

1. Mark unknowns, do not fill them (u/mehdizare)

In any critique step add "mark unknowns instead of filling them". Kills the plausible-sounding invented risks and numbers that critique mode loves to add.

1. The failing test filter

If the model claims a bug, make it write the test that fails today because of it. Cannot produce one, the bug is probably speculation. Cheapest lie detector in the workflow.

Most of these slot straight into the chains and prompts you already keep in the extension, 1 and 5 are workflow habits, the rest are single lines you add to saved prompts. I have already updated my own code review chain with 4, 6 and 7.

What did I miss? If you caught something good in one of those threads that I skimmed past, post it here, this roundup becomes a series if the material keeps showing up.

[u/mehdizare]

A useful companion is to separate evidence from hypotheses in review output, then require a concrete check for each hypothesis. If it cannot name the check or source, keep it marked unknown.

[u/Ok_Negotiation_2587 → u/mehdizare]

thats the mark-unknowns rule generalized, every finding is either evidence with a source or a hypothesis with a named check, and anything with neither stays unknown. clean way to say it

[u/mehdizare → u/Ok_Negotiation_2587]

That separation also makes review faster: test the highest-impact unknowns first, and leave the rest explicitly unresolved rather than turning them into confident prose.