Bug to BranchGitHub
Test sandbox · not a product

Testing BugDrop with GitHub Issues

This page exists to try BugDrop end to end: send a report, see it land as a GitHub issue in this repo, and let a local Claude Code agent triage it. Test reports are welcome.

Send a test reportView issues

What’s being tested

  • BugDrop widget

    The hosted widget loads on every page and collects a category, title, description, and optional screenshot.

    Live

  • Report → GitHub issue

    Each report opens a public issue in this repo, labeled bugdrop plus bug, enhancement, or question, with browser info attached.

    Live

  • Triage agent

    A Claude Code skill (/triage-bugdrop) reads new issues and handles them by type. It runs on a maintainer’s machine about every 30 minutes, only while that session is open.

    Local

What happens to your report

  • Bug

    bug

    The agent finds the root cause, fixes it in a draft pull request, and links the PR on your issue. A maintainer reviews before anything is merged.

  • Feature

    enhancement

    The agent posts a plan as a comment and waits. Work starts only after a maintainer replies “ok”; any other reply keeps it pending.

  • Question

    question

    The agent replies with an answer based on this repo’s README, docs, and code, or says plainly if the repo can’t answer it.

How to test it

  1. Step 1

    Open a broken page below, spot something wrong, and click the Feedback button.

  2. Step 2

    Pick Bug, Feature, or Question, write a short title, and add a screenshot if you like.

  3. Step 3

    Find your issue in the Issues tab. If the triage loop is running, expect a reply within about 30 minutes.

Broken pages to report

Each page has several deliberate UI bugs. Report whatever you find.

Before you submit

  • Every report becomes a public GitHub issue, so leave out anything private.
  • Screenshots are stored on the repo’s bugdrop-screenshots branch.
  • Test issues may be closed or deleted at any time.