github-issue-creator

Topics in the source

• GitHub Issue Creator
• Output Template
• Output Location
• Guidelines
• Examples

Transform messy input (error logs, voice notes, screenshots) into clean, actionable GitHub issues. [Error message/code if applicable] Create issues as markdown files in /issues/ directory at the repo root. Use naming convention: YYYY-MM-DD-short-description.md 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 [PROJECTNAME], [USERID], 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, cosmetic Image/GIF handling: Reference attachments inline. Format: Description Input (voice dictation): so I was trying to deploy the agent and it just failed silently no error nothing the workflow ran but then poof gone from the list had to refresh and try again three times Output: -- Input (error paste): Error: PERMISSIONDENIED when pu

This is an excerpt. Refer to the complete source and its current requirements.