Address Feedback
Go through a feedback list (Notion, Google Doc, Linear, GitHub issue, pasted notes) and...
Install
npx skills add BuilderIO/agent-native --skill address-feedback -g -a claude-code -y- Repository
- BuilderIO/agent-native7.6k
- Category
- Design
- Updated
- 3d ago
- License
- MIT
- Context cost
- Lightabout 1,229 tokens
- Runs scripts
- No, instructions only
What it does
Go through a feedback list (Notion, Google Doc, Linear, GitHub issue, pasted notes) and fix the real bugs, propose small UX changes, and flag the rest. Use when someone shares a feedback link or paste and says "address this feedback", "fix the bugs in this doc", or runs /address-feedback. For Slack feedback channels use review-latest-feedback; for specific Slack threads use address-feedback-with-replies.
Address Feedback
Take a pile of feedback, fix what is objectively broken, verify it, and report
back briefly. Lean toward fixing, but don't agree with every suggestion or
bundle unrelated cleanups. If no link or text was given, ask for it. Use the
matching connector (Notion, Drive, Linear, gh, Slack) rather than scraping
authenticated pages. Slack reactions and replies follow review-latest-feedback.
1. Read it and check for repeats
Read the whole source, including comments, screenshots, and linked recordings. The error text in a screenshot is often the diagnosis.
Then check whether it was reported before; the same defect gets filed weeks apart by different people, and one came back fifteen times. Search three months back: the source, Sentry, Analytics errors, and merged PR titles, using the feature name, error text, and surface separately.
- No earlier report: carry on.
- Earlier report, no fix: say how long it has been open.
- Earlier report, fix landed: a regression. Find why the first fix stopped holding and leave a test of the user's path that fails if it breaks again.
2. Sort each item
Checklist each item: symptom, expected behavior, evidence, owning surface.
