What problem does it solve? Technical questions posted in GitHub Discussions, issues, or team channels often lack the information maintainers need to act, leading to ignored threads and wasted back-and-forth. This Skill turns vague reports like "it doesn't work" into answerable questions with a complete, minimal information set. ## Core Features & Use Cases - Mandatory information checklist: Enforces version/environment details, minimal reproduction steps, expected vs. actual behavior, full untruncated error output, and a list of solutions already tried. - Title and pre-submission guidance: Provides a symptom-plus-condition title formula and a pre-flight checklist (read docs, search existing issues, test another environment, confirm it is a real bug). - Feature request framing: Guides writing proposals that state the underlying problem first, current workarounds, and honest beneficiary scope. - Use Case: Before opening an issue about skills not loading, use this Skill to produce a report with exact versions, a minimal repro in /tmp, the full error log with credentials redacted, and a searchable title. ## Quick Start Help me write a GitHub issue about my tool failing to load config files, following the ask-good-questions checklist.
