bug
/bug
Report a handoff-terminal bug on GitHub. Use when the user wants to report a problem with the handoff-terminal plugin. Collects the versions and a log with sites, ids and paths removed, shows the user the report, and sends it only after a clear yes.
- Author
- lucas-saldanha-werneck ↗
- Repository
- handoff-terminal ↗
- Licence
- MIT
- Last repository change
- 13.11.2026
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 13.11.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Report a handoff-terminal bug on GitHub. Use when the user wants to report a problem with the handoff-terminal plugin. Collects the versions and a log with sites, ids and paths removed, shows the user the report, and sends it only after a clear yes.
Arguments
/bug [what went wrong]
Original author description
Report a handoff-terminal bug on GitHub. Use when the user wants to report a problem with the handoff-terminal plugin. Collects the versions and a log with sites, ids and paths removed, shows the user the report, and sends it only after a clear yes.
How it works
- Purpose
- Instructions
- Prerequisites
- Limitations
- Troubleshooting
- Examples
SKILL.md preview
---
name: bug
description: 'Report a handoff-terminal bug on GitHub. Use when the user wants to report a problem with the handoff-terminal plugin. Collects the versions and a log with sites, ids and paths removed, shows the user the report, and sends it only after a clear yes.'
argument-hint: "[what went wrong]"
disable-model-invocation: true
version: "0.7.10"
metadata:
author: Lucas Saldanha Werneck <lucas@2olhares.com>
tags: [bug-report, github, support]
---
# Report a handoff-terminal bug
## Purpose
Let the user report a handoff-terminal bug in one step: a draft report with versions and a cleaned log, shown in full before anything is sent.
The user wants to report a bug in the handoff-terminal plugin. What they typed: $ARGUMENTS
## Instructions
1. If they did not say what went wrong, ask in one short question. Wait for the answer.
2. Write the problem in 1–3 plain sentences: what they did, what they expected, what happened.
Leave out passwords, codes, card numbers, emails, names, addresses and site names.
3. Run this, with the sentences between the two `EOF` lines. The quoted `'EOF'` keeps the shell
from running anything inside the text (`$(...)`, backticks):
```
python3 "${CLAUDE_PLUGIN_ROOT}/bin/handoff-bug" draft - <<'EOF'
<the sentences>
EOF
```
4. Show the user the whole report exactly as printed, and a short title (under 80 characters).
Ask: "Send this to GitHub?" Say that the issue is public.
If they want changes, edit the report file printed after `REPORT FILE:` and show it again.
5. Only after a clear yes, run (the title goes between the `EOF` lines the same way):
```
python3 "${CLAUDE_PLUGIN_ROOT}/bin/handoff-bug" send "<report file>" --title - <<'EOF'
<title>
EOF
```
6. Give the user the link it prints. If it opened the browser, tell them to press Submit there.
Never send without the yes. Never add anything to the report that the user did not see.
## Prerequisites
- python3 (3.8+) and the handoff-terminal plugin enabled.
- Optional: a signed-in gh CLI. Without it, sending opens the browser on a new issue with the report already filled in.
## Limitations
- The issue is public: the user must see and approve the whole report first.
- Names, passwords, codes, addresses and site names are left out of the sentences; the log has sites, ids and paths removed.
## Troubleshooting
- Error "no report at ...": the draft step was skipped. Run it first.
- Error from gh (it could not create the issue): the tool says so and uses the browser instead; tell the user to press Submit there.
## Examples
- `/handoff-terminal:bug the terminal session opened but the app never continued`: writes the problem in a
few plain sentences, runs `handoff-bug draft`, shows the whole report and a short title, and asks
"Send this to GitHub?". Only after a clear yes does it run `handoff-bug send` and give the link.
- `/handoff-terminal:bug` with nothing after it: asks in one short question what went wrong, then continues the same way.
- The user wants a change to the draft: edit the report file printed after `REPORT FILE:` and show it again before asking.
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · lucas-saldanha-werneck/handoff-terminal | 100 | MIT |
| Perchusha/pitwall | 100 | MIT |
| jisuzzzz/haechi | 100 | MIT |
| paulhowever/orchestor | 100 | MIT |
| foxrun-ai/foxrun | 100 | MIT |
| AtT6669/dsh-go-root | 82 | AGPL-3.0 |
Database snapshot: 13.11.2026 · package version c33b41c04ab6 (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
- 86file-issue
File a bug, feel/balance report or idea in the game's GitHub Issues from what Claude found (a review, a playtest, a bug hunt that is not fixed now), safely - a dry run shows the exact title, labels and body first, private content (keys, local paths, emails, private words) is… - 100report-issue
Use when the user wants to report a bug, file an issue, submit a bug report, or report any problem with the mobile-app plugin. - 100zoonk-bug-report
File a Zoonk bug report on GitHub for anyone, technical or not, in any language. Ask in their words for what's missing, write the issue in English and keep private details out. Use when someone asks you to report a bug or a problem in Zoonk. - 100report-bug-ce
Use this skill when a user needs to report a bug in the Systematic plugin with complete reproduction details and environment data, then open a GitHub issue directly from the CLI. - 87file-bug
Use when the user wants to file a bug, open a GitHub issue, raise a ticket, log this as a bug, or otherwise create a tracked record of a symptom against switchroom (or another configured repo). Pulls the right log files automatically, forces a root-cause section with citations,… - 90plugin-feedback
Report friction with the rossum-sa plugin as a sanitized, human-confirmed GitHub issue or anonymous maintainer-reviewed report. Use when the SA hits a capability gap, a tool bug, or a wrong/ missing Rossum fact, or when the friction detector offers to log it. Triggers on "log…