fix: tighten caveman full output#322
Conversation
be81ced to
e943435
Compare
SummaryThis PR tightens the existing The goal is to keep
Standard technical acronyms are still allowed. The rule is meant to preserve clarity, not make output more formal. Before
That costs tokens and makes answers slower to read, especially when the useful part is only one specific failure phrase. After
This keeps the mode compact without making technical answers cryptic. Verifier updateWhile testing locally on Windows, I hit a case where The verifier now falls back to Git Bash when available, so local verification can still run the Unix hook install/statusline checks. TestingLocal checks passed:
Also verified that tracked public files do not contain private shorthand/research wording. AI DisclosurePrepared with GitHub Copilot assistance GPT 5.5 |
Tightens caveman full output to avoid verbose tool narration, tables, emoji, and long error dumps unless explicitly requested.
Also clarifies that standard technical acronyms are fine, while invented/ambiguous abbreviations should be avoided, and improves the verifier on Windows/Git Bash.