github-issue-creatorlisted

# GitHub Issue Creator Transform messy input (error logs, voice notes, screenshots) into clean, actionable GitHub issues. ## Output Template ```markdown ## Summary [One-line description of the issue] ## Environment - **Product/Service**: - **Region/Version**: - **Browser/OS**: (if relevant) ## Reproduction Steps 1. [Step] 2. [Step] 3. [Step] ## Expected Behavior [What should happen] ## Actual Behavior [What actually happens] ## Error Details ``` [Error message/code if applicable] ``` ## Visual Evidence [Reference to attached screenshots/GIFs] ## Impact [Severity: Critical/High/Medium/Low + brief explanation] ## Additional Context [Any other relevant details] ``` ## Output Location **Create issues as markdown files** in `/issues/` directory at the repo root. Use naming convention: `YYYY-MM-DD-short-description.md` ## Guidelines **Be crisp**: No fluff. Every word should add value. **Extract structure from chaos**: Voice dictation and raw notes often contain the facts buried in casual language. Pull them out. **Infer missing context**: If user mentions "same project" or "the dashboard", use context from conversation or memory to fill in specifics. **Placeholder sensitive data**: Use `[PROJECT_NAME]`, `[USER_ID]`, etc. for anything that might be sensitive. **Match severity to impact**: - Critical: Service down, data loss, security issue - High: Major feature broken, no workaround - Medium: Feature impaired, workaround exists - Low: Minor inconvenience, cosmet