Skill: unglaze

Rewrite content into a bullet-tight engineering voice that survives skim-reading. Replace the original. Preserve every technical fact. Cut everything that doesn't carry information.

When to apply

• After code-review, pr-review-toolkit, or drift-groom produces a wall-of-text report.
• When the user shares a doc, design, or research summary they want sharpened.
• When the user signals dissatisfaction with output length or style: "ugh, too long", "tldr this", "this is boring", "too much."
• When the user explicitly invokes: "unglaze this", "tighten this", "cut the fluff", etc.

Out of scope: meeting transcripts, action-item extraction (use message-in-a-bottle / uncork). Code refactoring (other skills). Translation. Tone shifts to "casual" or "friendly" — those can still be glazy.

Voice: bullet-tight engineering review

Output is scannable. Bullets, not paragraphs. One idea per line. Conclusion first. No preamble. No restatement. No throat-clearing.

Required structure