Turn Kiro problems into clear English reports and route them to the right support channel. Use when the user hits a bug, unexpected error, setup issue, MCP problem, steering/spec behavior, platform-specific issue, or product feedback and wants help collecting evidence, filling missing details, choosing Discord tags, or drafting a report for Discord or GitHub Issues.
Help the user troubleshoot Kiro problems first, then convert unresolved issues into submission-ready English reports. Triage the issue first, ask only for the missing facts that matter, and recommend the right channel instead of forcing every case into a bug report.
Match the user's language during the interactive part of the workflow. Infer that language primarily from the user's current and recent messages, not from system locale. Ask follow-up questions, explain routing decisions, and summarize missing information in the same language the user is using. Only the final deliverable for external reporting should default to English.
When the recommended channel is Discord, generate the final output in a Discord-friendly format with the post title and post body clearly separated.
Keep tag suggestions outside the copy-ready blocks. Discord tags are selected manually in the UI, so do not mix them into the title or body that the user may want to copy with one click.
For Discord outputs:
If the runtime allows local command execution, use the helper script from the global skill directory to gather the installed Kiro version and OS details before asking the user to type them manually.
Do not assume the current working directory is the skill folder. Resolve the script path explicitly, for example:
python3 ~/.kiro/skills/kiro-bug-report/scripts/collect_kiro_env.py --markdownStart with the lightest useful troubleshooting step before moving into formal reporting.
Goal:
If the issue appears resolved during troubleshooting:
If the issue remains unresolved, continue to classification and reporting preparation.
During troubleshooting, suggest a short search pack the user can try before escalating:
Build the search pack with these heuristics:
replying, responding, stuck, keep, or repeatsthis keeps happening, recent builds, or latest versionOnly switch the search keywords away from English if the user explicitly asks for localized search terms too.
Start by deciding which bucket fits best:
Bug: clearly broken or incorrect behaviorSetup Issue: install, configuration, onboarding, or environment problemsMCP Issue: schema, tool registration, integration, or tool behavior problemsSteering or Specs Issue: behavior shaped by steering/spec files or related workflowsPlatform Issue: macOS, Windows, or Linux specific behaviorAccount Issue: authentication or billingFeedback: product suggestion or UX complaintUsage Question: the user is unsure how Kiro is supposed to workDo not guess a root cause. If the category is uncertain, say so and choose the closest working label.
Escalate only when at least one of these is true:
If escalation is not justified yet:
Recommended Next ActionPrevention TipsWhen to ReportAsk short follow-up questions only for the information still needed to produce a useful report:
When available, run python3 ~/.kiro/skills/kiro-bug-report/scripts/collect_kiro_env.py --markdown and paste its output directly into the final report. Use the default JSON output only when structured data is more useful than paste-ready text.
If the helper script cannot be found or executed, fall back to asking the user for Kiro version, OS, and architecture instead of failing the workflow.
If the user has limited information, do not block. Produce a draft anyway and list the missing items clearly.
During this information-gathering stage, keep all questions and explanations in the user's language unless the user explicitly asks to switch languages.
Before routing the issue, compare it against the known quick-check cases in references/routing-notes.md.
If the issue matches a known pattern:
If more evidence is needed, suggest Help > Toggle developer tools.
Use the troubleshooting templates in references/troubleshooting-templates.md to choose the best Troubleshooting Attempted section:
unexpected error template when the report matches the known FAQ patternOnly enter this phase when the issue should be escalated.
If the issue does not need escalation, do not generate a formal Discord or GitHub report. Instead, give a compact troubleshooting outcome in the user's language with:
Always write the final external-facing deliverable in English.
Before the final report, you may briefly explain what you are doing or what is still missing in the user's language.
When useful, include a short Suggested Search Keywords section before the final report so the user can quickly check for similar reports before posting. The section label or explanation may follow the user's language, but the keyword list itself should default to English.
If the first search pack is too narrow, provide a second-pass fallback pack with shorter and looser variants.
Use references/discord-template.md when the route is Discord.
Use references/github-template.md when the route is GitHub Issues.
Use references/non-escalation-templates.md for the compact closure format when the issue does not need escalation.
Replace the placeholder Troubleshooting Attempted section in those templates with the most relevant checklist from references/troubleshooting-templates.md. Keep only the lines that actually fit the case.
When the route is Discord:
Discord Post TitleDiscord Post BodyRecommended Tags as a manual suggestion list for the user to apply in the Discord UIRecommended Tags outside the copy-ready Discord title and body blocksWhen the route is GitHub Issues:
GitHub Issue TitleGitHub Issue Bodyreferences/github-template.mdreferences/github-template.md based on issue typeUse the routing notes in references/routing-notes.md.
Default routing rules:
Usage Question or Setup Issue -> DiscordTroubleshooting First, then Discord if still reproducibleAccount Issue -> official account-related channelMCP Issue, Steering or Specs Issue, or platform-specific behavior -> Discord with focused tagsWhen recommending Discord:
When recommending GitHub Issues: