Skip to content
Skills Library
Programming · Writing

bug

/bug

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.

Repository
dsh-go-root ↗
Licence
AGPL-3.0
Last repository change
14.11.2026

Assessment and security

82/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content17 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 14.11.2026, without references to retired models or APIs.

Licence

AGPL-3.0, copyleft: przeróbki udostępniane innym muszą mieć tę samą licencję.

What it does and when to use it

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.

Original author description

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.

How it works

SKILL.md has no level-two headings · 10 lines, 175 words

SKILL.md preview
---
name: bug
description: 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.
---

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.

1. Extract the symptom, expected behavior, and reproduction details already supplied. Inspect available logs and relevant code before asking for facts the workspace can provide.
2. Ask only for missing information that materially affects reproduction or diagnosis, such as Android version, host connection type, device model or the triggering input. Continue independent investigation while waiting; label unknowns instead of guessing.
3. 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.
4. 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.

Versions

RepositoryScoreLicence
This page · AtT6669/dsh-go-root82AGPL-3.0
Perchusha/pitwall100MIT
lucas-saldanha-werneck/handoff-terminal100MIT
jisuzzzz/haechi100MIT
paulhowever/orchestor100MIT
foxrun-ai/foxrun100MIT

Database snapshot: 13.11.2026 · package version 2d128339ba96 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 90propose-issue
    Use when the user asks to propose an issue, file or open a bug report, or turn a reported defect into a tracked issue. Not for fixing the defect, triaging existing issues, or reviewing PRs.
  • 100create-bug-report
    Create a structured bug report when the user reports a bug, wants to file an issue, document a defect, or needs help writing a bug report with proper reproduction steps
  • 100validator-issue
    Files structured GitHub bug reports for agent-validator when users ask to file, report, or open an issue for a suspected defect
  • 90filing-bug-reports
    Generate a standalone bug report that another developer can use to reproduce, investigate, and fix an issue. Use when the user says 'file a bug', 'write a bug report', 'report this issue', or asks to document a defect for handoff.
  • 100report-bug
    Creates structured bug report documents with reproduction steps, expected vs actual behavior, and severity classification. Use when the user asks to "report a bug", "file a bug", "document a defect", "log an issue", or mentions a bug, defect, regression, or unexpected behavior…
  • 90propose-issue
    Use when the user asks to propose an issue, file or open a bug report, or turn a reported defect into a tracked issue. Not for fixing the defect, triaging existing issues, or reviewing PRs.

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.