AugmentClaude

Bug Report Generator

Capture bug details and create structured reports your team can act on.

Installation

  1. Make sure Claude is on your device and in your terminal.

    Skills load from ~/.claude/skills/ when Claude Code starts up — so you need it on your machine first. If you don't have it yet, install it once with the command below, then run claude in any terminal to verify.

    One-time setup
    npm i -g @anthropic-ai/claude-code

    Already have it? Skip ahead.

  2. Paste into Claude Code or into your terminal.

    This copies the whole skill folder into ~/.claude/skills/bug-ccch1mneyyy/ — the SKILL.md plus any scripts, reference docs, or templates the skill ships with. Safe default: works for every skill.

    Faster alternative (instruction-only skills)

    Skips the clone and grabs only the SKILL.md file. Don't use this if the skill ships Python scripts, reference markdowns, or asset templates — they won't be downloaded and the skill will fail when it tries to load them.

    Quick install (SKILL.md only)
    Sign up to copy
  3. Restart Claude Code.

    Quit and reopen Claude Code (or any other agent that loads from ~/.claude/skills/). New skills are picked up on startup.

  4. Just ask Claude.

    Skills auto-activate when your request matches the skill's description — no slash command needed. Trigger phrases live in the skill's own frontmatter; you can read them in the “What this skill does” section above.

Prefer to read the source first? Open on GitHub.

When Claude uses it

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.

What this skill does

Bug Report

Capture a complete, actionable bug report. Ask only the questions needed to fill genuine gaps — never interrogate the user.

Procedure

  1. Understand the symptom: what happened vs what was expected. If the user already gave enough detail, skip straight to the report.
  2. Fill any critical gaps with at most 2-3 targeted questions: reproduction steps, environment (OS/terminal/node version), and whether it's deterministic.
  3. If the codebase is available, inspect the suspected area to add root-cause hypotheses (with file/line evidence where possible).
  4. 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.

Related skills