At a glance
What it does
Turn a reported bug into a structured, actionable report.
Before you choose it
Turn a reported bug into a structured, actionable report. The supplied pinned skill document describes its trigger and workflow.
Best for
Users who need this workflow in a DSH project.
Common tasks
- Turn a reported bug into a structured, actionable report.
Permissions and data
The skill guides a local workflow; external behavior is not independently audited.
Permissions- Uses the documented skill workflow.
- Data handling was not independently audited.
- External services follow the supplied project instructions.
- Credential requirements were not independently tested.
Limitations
- The skill document does not establish runtime compatibility.
What DSHub checked
- The source commit and complete skill document were captured.
What DSHub did not check
- Installation and runtime behavior were not tested.
Pinned install
Primary action
This standalone skill does not have a DSH Plugin install action. Use its source documentation for the delivery method.
Maintainer source
Skill instructions
name: bug description: Use when the user reports a bug or asks to capture one — ask the minimal questions needed, then produce a structured bug report the team can act on.
Bug Report
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.
Operate deliberately
Install and manage
Prerequisites and target Profile
Target： No native DSH Profile target.
Delivery： Skill Files — https://github.com/ccch1mneyyy/dsh-tui。
Compatibility and access
Requires_host_review： Not established by supplied evidence。
Review compatibility evidence ↗
Risk facts
Review instructions before use.
Evidence ↗Evidence and editorial reviewManifest, Bundle patch, distribution and freshness
Immutable evidence
Review status and source activity
Approved for publication after reviewing the source-linked content and immutable release record. AI assisted with the draft; the publication decision was human.
Human reviewed Aug 29, 2026, 3:18 PM UTC。GitHub facts last checked Aug 20, 2026, 2:01 PM UTC。
No material source change has been recorded since this evidence baseline.