caveman

To make responses shorter while keeping technical accuracy, apply a brevity transformation that removes filler, articles, and pleasantries while preserving exact code blocks and domain terms. This ensures high-density communication without losing actionable meaning.

Response compression for token efficiency is rewriting explanations into high-signal language by stripping hedging and verbal preamble. This lowers output token usage and accelerates reading while maintaining the exact technical fidelity required for debugging.

To get concise explanations for code review commentary, trigger a controlled response style that enforces brevity. This rewrites verbose feedback into direct, high-clarity statements while keeping domain terms and code snippets unchanged for accurate reviews.

Yes, concise response mode preserves exact error text and code blocks. While it removes filler words and articles to achieve brevity, it strictly keeps domain terms and code unchanged so the technical answer remains correct and actionable.

You should not use brevity transformations when the workflow requires conversational tone, detailed verbal preamble, or pleasantries. Because this response compression removes articles and hedging, it is unsuitable for contexts demanding standard conversational flow.