使用方法
- 复制安装命令,在自己的智能体环境安装前先检查源码包。
- 从原始文档核对所需工具、凭据和支持的宿主。
- 说明输入材料与期望交付物,并对照来源检查输出。
npx skills add https://github.com/ccch1mneyyy/dsh-tui --skill bug开始前需了解
- 安装不包含模型订阅、API 额度或访问文件的权限。
- 仓库星数和安装量反映活跃情况,不等于独立质量或安全测试。
按源仓库内容呈现,保留标题、案例、代码、表格、链接以及原文引用的演示图片。
Produce a concise report another person can reproduce or investigate. If the user asked for a fix, use the report as working context, continue the repair, and validate the result.
- Extract the symptom, expected behavior, and reproduction details already supplied. Inspect available logs and relevant code before asking for facts the workspace can provide.
- Ask only for missing information that materially affects reproduction or diagnosis, such as terminal mode or the triggering input. Continue independent investigation while waiting; label unknowns instead of guessing.
- Include the symptom in the title, then the smallest known reproduction, expected versus actual result, relevant environment, and impact. Distinguish a reproduction you ran from one reported by the user.
- Include a cause or workaround only when evidence supports it; label hypotheses and cite the relevant code. Omit empty sections and speculative severity labels.
Keep credentials and private session content out of the report. Drafting a report does not itself authorize posting an issue; use any posting authorization already given in the conversation.

