Install once.
Add the skill to Claude Code or Codex. Invoke it from the app you want to improve.
OPEN SOURCE · MIT LICENSE
Better bug reports.
Built into your app.
Give your coding assistant the skill to build a feedback flow that feels native to your product. Useful reports. Your infrastructure. GitHub or Linear.
An AI coding skill. Not a subscription. Not another SDK.
Share feedback
Something not quite right?
Tell us what happened. We’re listening.
Summary
The save button stays disabled
What happened?
I changed my display name, but couldn’t save the update.
Capture, review, then send. No background recording.
An actionable issue, in your tracker.
GitHub or Linear · delivered by your backend
Works with the way you build.
Next.js / ReactReact Native / ExpoFlutterSEE IT IN ACTION
Show more. Explain less.
A walkthrough of the real flow: describe the problem, select an element, annotate a screenshot, and review what gets shared.
Read the video transcript
Good feedback starts with context. Here is the feedback experience built into this website. Choose a category, add a short summary, and explain what happened. The microphone buttons also offer voice input in supported browsers.
Select the exact element you are talking about. Its location and structure stay with the report, without copying page text or form values. Attach a screenshot, then mark it up with arrows, shapes, and labels. Save the image back into your report.
Screen recordings, audio, and files are available when you need more context. Diagnostic collection is optional, and starts switched off. Review the text, screenshot, and selection together. On this site, report text is public, attachments are private, and publishing requires sign in.
Install the open source skill, then ask your coding assistant to connect GitHub or Linear. Make useful feedback part of your product.
FROM “IT’S BROKEN” TO SOMETHING USEFUL
A small widget.
A much shorter feedback loop.
It’s a set of instructions and implementation patterns for your AI coding assistant—not a hosted feedback service.
Make it yours.
Your assistant adapts the UI, authentication, and server endpoint to your stack and design system.
Close the loop.
Route reports to a confirmed GitHub repository or Linear team. You own the implementation and the data flow.
TWO COMMANDS. THEN MAKE IT YOURS.
Your next useful
report starts here.
Open Claude Code in your app’s project. Add the community marketplace, install the plugin, then use the prompt below.
Download the ZIP instead Installing in Codex?Free under MIT. Your coding assistant and issue tracker may have their own costs. Each installer connects their own accounts.
In Claude Code
/plugin marketplace add alibad/feedback-widget
/plugin install feedback-widget@feedback-widgetTHEN ASK YOUR ASSISTANTChoose your tracker
/feedback-widget:add-feedback-widget Add the full feedback experience using Linear. Reuse my app's authentication and design system. Ask me to confirm the destination team. Include screenshots and annotation, one element picker that works on unlabeled elements without collecting page text or form values, screen recording, audio attachments, and private attachments. Add voice-to-text dictation for Summary and What happened with one-tap mic start, live text directly in each field, Stop, Cancel, and Undo. Preserve the original text and caret, stop the microphone on dismissal or tab hiding, and avoid a separate transcript form or Insert step. Disclose speech-service processing before microphone access and provide an unsupported-browser fallback. Make diagnostics opt-in, require capture consent, and let reporters review everything before sending. Configure private storage and server-only tracker credentials. Do not create a live test issue without asking.
Tracker credentials belong on your server, never in the app bundle.
USEFUL CONTEXT. DELIBERATE BOUNDARIES.
Feedback shouldn’t
mean collecting everything.
Capture on your terms.
Screenshots, recordings, and diagnostics are deliberate choices. Review every capture before sending. No background recording or automatic collection of your screen.
Keep secrets server-side.
Use your own backend, scoped tracker credentials, authentication, and rate limits. The skill ships no tokens, team IDs, or preconfigured destinations.
No account with us.
The plugin adds no author-operated collector, analytics hook, or hosted feedback account. Review generated code before shipping; the AI tools you use have their own data policies.
These are implementation guardrails, not a privacy certification. You choose what your app collects and where it goes.
LIVE EMBEDS, NOT CAPTURES
Tap the real product.
Open its real feedback.
The phone is a live iframe, not a screenshot. Scroll it, sign in when needed, and use each product's own feedback controls without leaving this page.
Find feedbackOpen Settings → Send feedback, or report a problem from an exercise.
Open Stack Quest in a full tab These are production URLs. Authentication and submitted feedback stay with the embedded product.
Interactive production surface · clicks and scrolling enabled
Stack Quest
- Screenshot + annotation
- Dictation
- Voice
- Recording
DoneOS
- Screenshot + annotation
- Recording
- Durable outbox
Leela Quest
- Screenshot + annotation
- Dictation
- Voice
- Offline outbox
Cold Club
- Screenshot + annotation
- Voice
- Recording
- Diagnostics
Yoga Quest
- Screenshot + annotation
- Dictation
- Voice
- Recording
Scribe Quest
- Screenshot + annotation
- Attachments
- Categories
Six shipped implementations, audited from source. The exact feature mix follows each product’s risk, platform, and workflow; credentials stay server-side in every case.
GOOD FEEDBACK IS A FEATURE.