Bug Report
SkillDocs & knowledgeLets your agent turn a bug report into a structured writeup with symptoms, repro steps, and root-cause hypotheses.
Available today. Use it from your connected AI after setup.
No other account needed.
Connect ahel once, and every AI you use reads what you have installed.
Then ask your AI: use the Bug Report skill
About this capability
Turn a reported defect into an actionable bug report or issue draft. Use when the user asks to capture or document a bug; a request to fix broken behavior should proceed to diagnosis and repair.
What this skill tells your AI
The instructions your AI receives, as published by ccch1mneyyy/dsh-tui in .agents/skills/bug/SKILL.md and read by ahel’s review.
Capture a complete, actionable bug report. Ask only the questions needed to fill genuine gaps — never interrogate the user.
Procedure
- Understand the symptom: what happened vs what was expected. If the user already gave enough detail, skip straight to the report.
- Fill any critical gaps with at most 2-3 targeted questions: reproduction steps, environment (OS/terminal/node version), and whether it's deterministic.
- If the codebase is available, inspect the suspected area to add root-cause hypotheses (with file/line evidence where possible).
- Produce the report:
- 标题: one-line symptom summary
- 现象: observed vs expected behavior
- 复现步骤: minimal steps, with inputs
- 环境: OS / node version / dsh-tui version / terminal
- 影响: severity + who/what is affected
- 根因假设: evidence-based guesses, clearly labeled as hypotheses
- 建议: fix direction or workaround
Constraints
- Never invent reproduction steps or environment details — mark unknowns as "待确认".
- Keep the report tight; a bug report is a working document, not an essay.
Signals
- GitHub stars
- 3k
- Forks
- 176
- Last commit
- Sep 2026
Advanced
- Catalog kind
- skill
- Gateway key
bug- Source
- github.com/ccch1mneyyy/dsh-tui