feedback
/feedback
Report a bug, ask for a feature, or send feedback about pair as a GitHub issue on blackbeard-tech/pair. Use when the user says /pair:feedback, "report this", "file a bug", "this is broken", "pair should…", or complains about pair.
- Author
- blackbeard-tech ↗
- Repository
- pair ↗
- Licence
- Apache-2.0
- Last repository change
- 13.11.2026
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 1
No signals detected. Repository changed on 13.11.2026, without references to retired models or APIs.
Apache-2.0, otwarta: można używać i zmieniać, z zachowaniem licencji i informacji o zmianach.
What it does and when to use it
Report a bug, ask for a feature, or send feedback about pair as a GitHub issue on blackbeard-tech/pair. Use when the user says /pair:feedback, "report this", "file a bug", "this is broken", "pair should…", or complains about pair.
Triggers from the description
Arguments
/feedback [what happened or what you want]
Original author description
Report a bug, ask for a feature, or send feedback about pair as a GitHub issue on blackbeard-tech/pair. Use when the user says /pair:feedback, "report this", "file a bug", "this is broken", "pair should…", or complains about pair.
How it works
- 1. Gather the facts
- 2. One issue per problem
- 3. Write it
- 4. Keep private things out
- 5. Confirm, then post
SKILL.md preview
--- name: feedback description: Report a bug, ask for a feature, or send feedback about pair as a GitHub issue on blackbeard-tech/pair. Use when the user says /pair:feedback, "report this", "file a bug", "this is broken", "pair should…", or complains about pair. argument-hint: "[what happened or what you want]" --- Turn the user's feedback into a GitHub issue that a maintainer can act on without asking anything back: short, specific and complete. The user may give only a few words ($ARGUMENTS). Do the work for them. ## 1. Gather the facts Find out what you can yourself; don't ask the user for it: - **pair version:** the installed plugin's version. - **Claude Code version** and **OS**. - **Where it ran:** terminal, desktop app Code tab, VS Code or another IDE, `claude -p`, or a phone through Remote Control. - **Permission mode**, and the trust level if paired. - **What happened:** the exact error or message text, word for word, from this conversation or the tool results. - **Steps:** what was done just before, from this conversation. Ask the user only for what you still can't tell, usually what they expected instead, and ask everything in one message. Don't guess at causes. If you checked something (read the code, reproduced it), say what you found and how. ## 2. One issue per problem If the feedback covers several unrelated things, write a separate issue for each, and say so to the user. Before writing, look for an existing open issue on the same thing. If there is one, draft a comment that adds only what's new instead of a new issue. ## 3. Write it **Title:** the symptom or the request in plain words, under 80 characters, for example `send_file times out on files over 25 MB through the transit relay`. Not `Bug`, `Problem with pair` or `Feedback`. **Bug body.** Use only the sections that have something in them: ``` **What happened:** one to three sentences, with the exact error quoted. **Expected:** one sentence. **Steps:** 1. … **Environment:** pair 0.1.12 · Claude Code 2.1.309 · macOS 26.1 · desktop app Code tab · auto mode · trust read-only **Logs:** only the lines that matter, in a code block. ``` **Feature or feedback body:** the problem it solves (one or two sentences, with the real situation it came from), what they want, and anything they've already tried. Leave out greetings, thanks, apologies, background the maintainer doesn't need, guesses presented as facts, and any sentence that repeats another. If a sentence can go without losing information, take it out. ## 4. Keep private things out The repo is public. Remove or replace with placeholders: people's names, email addresses, usernames and hostnames (including inside paths, such as `/Users/<name>/`), pairing codes, the content of peer messages and files, project names and code that aren't the user's to share, and anything that looks like a token, key or password. Display names such as `user@host · name · email` count as private. ## 5. Confirm, then post Show the user the exact title and body, and post only after they say yes. Post to https://github.com/blackbeard-tech/pair/issues (with `gh issue create` if it's installed and signed in; otherwise give the user a new-issue link with the title and body filled in). Give them the issue's link at the end.
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · blackbeard-tech/pair | 100 | Apache-2.0 |
| shaunjones-gh/lilystack | 100 | MIT |
| superset-sh/superset | 100 | MIT |
| Embassy-of-the-Free-Mind/sourcelibrary-v2 | 100 | AGPL-3.0 |
| minanyang/10x-agent | 100 | MIT |
| Insilico-org/plsi | 100 | MIT |
| optimiziramsi/skills | 100 | MIT |
| AMDResearch/omniprobe | 100 | MIT |
| lykhoyda/qaren | 100 | MIT |
Database snapshot: 13.11.2026 · package version 8fc89290a131 (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
- 100create-github-issue
Create GitHub issues using the gh CLI. Use when the user wants to create a new issue, report a bug, request a feature, or create a task in GitHub. Trigger keywords - create issue, new issue, file bug, report bug, feature request, github issue. - 90studio-feedback
Prepare a user-reviewed Arch Studio bug report or feature request for GitHub. Use when the user runs /as:studio-feedback, says \"report a bug\", \"this skill broke\", \"send feedback\", or requests a feature. Do not use for Claude Code's native /feedback command. - 84github-issue
Use when opening a GitHub issue, bug report, feature request, or discussion in any repository, including one the user has no local checkout of. - 90feedback-intake
Help the user file a bug report or feature request for Nimbalyst. Activates when the user opens the in-app feedback flow or runs /feedback:bug-report or /feedback:feature-request. Coordinates evidence gathering, anonymization, and posting to GitHub Issues. - 100prisma-next-feedback
Hand a Prisma Next question or report off to the team — file a GitHub issue (bug or feature request), or route Q&A / design discussion / direct-team-contact to the Prisma Discord at pris.ly/discord. Use for bug, bug report, file an issue, report a bug, feature request, missing… - 90developer-feedback
Capture developer testing feedback as structured evidence and GitHub issues. Use when the user says "report feedback", "found a bug", "this doesn't work", "feedback on feature", "AC-XX is wrong", or reports an issue found during manual testing. Links feedback to acceptance…