boneskull/buggin

When a command-line app crashes unexpectedly, the default experience is usually a cryptic error message and a confused user who has no idea what to do next. buggin changes that. It intercepts those crashes and shows the user a friendly message with a direct link to create a bug report on GitHub, pre-filled with the error details. The goal is simple: turn silent failures into actionable bug reports. The setup is deliberately minimal. A developer adds one line of code to their app's entry point. When an uncaught error happens, the tool prints a notification to the screen with a link to the project's "new issue" page on GitHub, complete with the error message and stack trace already filled in. The user just clicks the link, reviews the pre-filled report, and submits it. Under the hood, it auto-detects the project name and GitHub URL from the app's configuration file, so there's almost no manual setup required. This is built for developers of command-line tools (CLIs) who want to close the gap between a crash and a bug report. Most users won't bother navigating to a project's repository, finding the issues page, and manually pasting an error. With this in place, a maintainer of a popular CLI tool can catch real-world failures they'd otherwise never hear about, and the user feels like the tool is actively helping them resolve the problem rather than just blowing up. A few tradeoffs are worth noting. It only works with GitHub-hosted projects, and only one package in an app can use it at a time. It also does not try to figure out whether an error originated from the developer's own code or from a third-party dependency, it just captures everything and lets the maintainer sort it out later. The developer can customize the message users see and filter out known, expected errors, though the README notes it's usually better to catch those proactively rather than letting them bubble up.