# Address Feedback

Go through a feedback list (Notion, Google Doc, Linear, GitHub issue, pasted notes) and...

- Repository: https://github.com/BuilderIO/agent-native (7579 stars)
- Category: Design
- License: MIT
- Last updated: 2026-11-01
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add BuilderIO/agent-native --skill address-feedback -g -a claude-code -y`
Codex: `npx skills add BuilderIO/agent-native --skill address-feedback -g -a codex -y`
Cursor: `npx skills add BuilderIO/agent-native --skill address-feedback -g -a cursor -y`
Gemini CLI: `npx skills add BuilderIO/agent-native --skill address-feedback -g -a gemini-cli -y`
Claude Code plugin marketplace: `/plugin marketplace add BuilderIO/agent-native`

## Description

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.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# 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.

The rest: https://github.com/BuilderIO/agent-native/blob/HEAD/.agents/skills/address-feedback/SKILL.md