-
Notifications
You must be signed in to change notification settings - Fork 117
Description
Problem
When triaging issue #1184 ("[Question] Console output hint color legibility"), the triage bot's comment opened with:
This is a known limitation of how hint text is styled in worktrunk.
This was inaccurate — there was no prior issue, no documentation, and no discussion about dim text legibility. The issue was newly discovered. Calling it a "known limitation" overstates the project's awareness and creates false expectations for the reporter.
The bot also provided a more detailed technical explanation than the skill template calls for, which was arguably helpful but included an inaccurate suggestion ("Adjusting your terminal's 'dim' rendering" — which Windows Terminal doesn't support, as the bot itself noted). The maintainer later identified the actual culprit as "dim bright black" (the combination of dim + bright-black styling), while the bot attributed it solely to the dim attribute.
The skill's question template says:
Thanks for reaching out! This looks like a usage question rather than a bug report.
[Brief answer if obvious from the codebase, or pointer to relevant docs/help text.]
A maintainer can provide more detail if needed.
The bot deviated from this by omitting the "a maintainer can provide more detail" footer and by adding authoritative framing that exceeded its role.
Observed in
Run 22313754838 triaging issue #1184.
Suggested approach
This is a judgment issue rather than a template gap — the template is already appropriate. Adding a note like "state facts you verified in the codebase; do not characterize something as 'known' unless you find prior issues or documentation about it" could help, but may be over-fitting to a single incident. Worth watching for recurrence before changing the skill.
Source
Nightly reviewer analysis of runs from 2026-02-23.