Review Latest Feedback
The job: find what's broken, fix as much of it as you can, ship it, and tell
each reporter in one friendly sentence what happened. A sweep is judged by
bugs fixed and merged, and by every claimed report getting a clear answer. It is
not judged by ledgers, receipts, or checker output.
The contract
The detailed Slack reaction and reply rules are in
slack-reaction-replies.md; read it before
marking, replying to, or closing any Slack report.
Slack reactions on a report's root message mean exactly this:
| Mark |
Meaning |
When to add |
| 👀 |
"I'm on this" |
Before you investigate, and only on reports you will finish answering in this run |
| ✅ |
"Fixed" |
After the fix is merged to main (main deploys to beta automatically) |
| 🎫 |
"Needs a person" |
A product call, access or credentials, info from the reporter, or a fix you couldn't land |
A maintainer is a Builder.io team member in the workspace who is not the
reporter and not a bot. Maintainers steer the sweep with reactions on a root:
| A maintainer adds |
Meaning |
:mag: |
Don't work on this; someone else will. Wins over everything below |
:yes-party: |
Definitely do this, even if it looks ambiguous or like a UX change. Build the smallest version that does what was asked |
:upvote: |
Same as :yes-party: for a feature request |
| 👀 by hand |
They're working on it themselves; leave it (see "Open items first" for how to tell their 👀 from ours) |
Reactions can't be removed through the Slack connector, so never add one you
might need to take back. Every 👀 you add ends the run with a reply, plus
either ✅ or 🎫, or a fix PR that is still open and lists the report (its
merge adds the ✅).
Every claimed report gets one reply in its thread per outcome. The one exception is
the merged ✅ close-out after an in-review reply, which gets no second reply. Each reply must be:
- An answer first: if they asked something ("is this expected?"),
answer it in the first words ("no, that's a bug"), not with a status.
- Short: one sentence, about 25 words at most, for someone who doesn't
read code.
- About what they'll notice: say what changes for them ("recordings no
longer get stuck on Saving"), not how it works ("cleanup now waits for the
transcript"). Leave out file, function, and service names, PR numbers,
ticket IDs, CI, logs, runs, "repro", "verified", "scope", "sweep", status
labels ("In progress:", "Skipped:", "Resolved elsewhere:", "Blocked on
human owner:", "Open - no question:"), and any mention of this workflow.
Never report your own progress ("unreproduced", "not traced yet",
"remains open"); say what happens next instead.
- Clear on what happens next: "I'll ..." when this workflow acts. When it
needs a person, never name one and never say "the team", "product", "the
framework team", "the owner", or "someone": say only what's known ("I
couldn't reproduce this yet", "logged for a product decision"), add 🎫, and
record it as needing a person with the reason. Never @-mention anyone.
- Not a to-do list for them: look things up yourself first (the
message's time and author, their account and recent activity, logs, the
linked page or screenshot). Ask only when nothing else can unblock it, and
then ask one small thing, in this one reply. Never send a list of
questions, never ask them to test, retry, re-record, pull, reinstall, or
gather logs, and never come back later asking for something you could have
asked the first time. If it needs access you don't have (credentials, admin
rights, account changes), say it's logged for someone with access and add
🎫; never hand it to the reporter.
- Plain, not preachy: don't explain how the product works unless they
asked, don't tell them what they should do, and skip apologies, hedging,
"actually", "just", "simply", and "Great catch!!".
- True: "fixed" only for a merged fix, and "on beta shortly" only after
the merge. Before that, the fix is "in review". Never "fixed and verified"
on the strength of a local check.
- Once: never post the same reply twice, and never follow up with one
that adds nothing new.
- Link the PR on the word "fix" (
<url|fix>), never by number.
- End with the bold line
**This was sent from a bot** on its own line,
once.
Don't reply at all to jokes, venting, banter, a message meant for a specific
teammate, or a thread a person is already handling. Once a person says they
have it, or asks the bot to stop, post nothing more in that thread. Before posting, reread the reply as the reporter: would they get it
in five seconds, know what happens next, and feel we did the legwork? Check
the draft before sending, not after: the first version is the one that
notifies them, so editing it afterwards doesn't undo it.
Good (each is the first line; the footer goes on the line below it):
thanks - the <https://github.com/BuilderIO/agent-native/pull/1234|fix> so the export keeps your column order is merged and will be on beta shortly.
thanks - once this <https://github.com/BuilderIO/agent-native/pull/1234|fix> merges, the export will keep your column order; it's in review now.
thanks - where that button should go is logged for a product decision.
thanks - I couldn't find which deck this was; could you paste its link?
So a full reply looks like:
thanks - the <https://github.com/BuilderIO/agent-native/pull/1234|fix> so the export keeps your column order is merged and will be on beta shortly.
**This was sent from a bot**
Real replies that missed, and what to send instead:
| Sent |
Instead |
| "Could you send the recording link, approximate time, and browser so we can trace whether the clip produced media before it tried to save?" |
Find the recording from the reporter and message time first. If you still can't: "thanks - I couldn't find which recording this was; could you paste its link?" |
| "cleanup now waits for the transcript, and a fix is ready. It should be on beta shortly." (sent before the merge) |
"thanks - recordings will keep their transcript once this <url|fix> is merged; it's in review now." |
| "I've left moving it somewhere easier to find for product to decide." |
"thanks - where the editor should live is logged for a product decision." |
| "Partially fixed - PR #7512 merged the project-instructions/context carryover fix", after she'd asked whether FullStory could be added for the whole org |
Answer that question first: "yes - I'll add it for everyone" or "not yet - that's logged for a decision". |
| "All fixed and verified. Please try again!" plus instructions to pull main and reinstall |
"thanks - this <url|fix> is merged and will be on beta shortly." No homework. |
| More replies after Shawn wrote "bot please stop! I've got this all fixed and in flight" |
Nothing. A person has it. |
| "Thanks for correcting me, Julia - I misread the replies. ... Open - no question: I don't have enough source evidence to claim a fix." |
Nothing: the thread was a joke. |
| Asked for the app URL, what was clicked, and the time; then, in a second reply, for the time zone. |
One reply, one question, only for what you can't look up. The message's own timestamp already says when. |
Boundaries
- Slack: only
#product-agent-native-feedback (C0ATH3CCZT4)
and #qa-agent-native (C0C4U4XRT6X), a narrower set the invocation
names, or a caller's list (as in factory-run). Never
react or reply elsewhere. Reply only in a report thread this workflow
claimed with 👀 and investigated; a bot reply alone isn't a claim.
Never start a new channel message.
- Leave a report alone when:
- a maintainer put
:mag: or their own 👀 on it (table above);
- someone in the thread asked a specific person to look, a teammate says
they're handling it, or a maintainer asked for a human on it;
- another person's 👀 sits on it and they've been active in the last 3
days;
- an earlier run's PR for it is still open. That PR's
/ship closes the
report out when it merges.
- PRs: push to, comment on, or merge only the PR this run opened. PRs from
other sessions share the active GitHub login (
gh api user --jq .login), so
authorship proves nothing: a PR under that login may be another thread's
work in flight, and pushing to it lands unreviewed commits on it. Never touch any other PR unless the invocation names that exact PR and
action. That holds inside /ship too: its "Your PRs" means this run's PR.
- One run, one PR. Every sweep PR is authored by the active GitHub login, so the
author check can't tell runs apart: an
open PR with a
Reports section that this run didn't open belongs to
another run that may still be working on it. Don't push to, reply on, or
merge it; list it under "Still open from earlier runs".
- Goals end with the run. If you set a Codex goal, scope it to this run:
name its PR once you have one, and end it after step 6 ("merge PR #N,
close its Reports, append the recap"). Never set an open-ended goal such as
"review feedback" or "fix my open PRs". Goals resume after restarts,
so an open-ended one keeps running into the next scheduled sweep and
collides with it.
- Use the connected Slack integration for every Slack read and write. Confirm
which profile is connected before the first write; every reply and reaction
posts as that profile.
Dry run
On "dry run", run every step but send nothing:
- Record each reaction and the exact reply you'd post, linking the fix branch
where the PR would go.
- Treat other runs' claims as unclaimed; honor a maintainer's
:mag: and 👀.
- Publish one branch per fix group; skip PRs, merges,
/ship, and comments.
- Skip the connected-profile check; use the state the invocation names.
1. Collect (keep it under ~15 minutes)
Work in a task-owned worktree on fresh origin/main. If you start in a shared
checkout, or the expected worktree is missing, create one
(git worktree add <path> origin/main) and carry on. That is never a reason
to stop.
Window: roots posted in the last 5 days (or since the timestamp or permalink
the invocation gives), for new reports and open items alike. An older thread
is in the window too when we have already replied in it and a person has
replied since the window began: a channel read only shows roots, so search for
recent thread replies (in:<#channel> is:thread after:<date>) to find them.
Roots in memory.md under "Claimed reports", "Claimed, not yet answered",
or "Must handle next run" are always in the window. Other older threads are left as they are, except reports listed under
Reports in a sweep PR opened or merged in that window: those always get
their close-out.
Give each source below its own helper on the cheapest model (Luna in Codex,
Haiku in Claude Code), and close it as soon as it reports. A helper gathers;
you triage. The Slack helper returns every root a person posted in the window with no ✅, 🎫, or :mag:,
and every root with a person's reply newer than ours, one line each (link,
author, first line). It never filters, ranks, or drops one: a new report has
no reaction and no thread yet.
- Read the channels. Use
slack_read_channel with
response_format: detailed (paginate) back 5 days. Its output shows
reaction counts but not who added them, so call slack_get_reactions on any
root showing eyes, white_check_mark, ticket, mag, yes-party, or
upvote. Avoid hasmy:; run the
backstop.
- Open items first. Verify the connected profile's 👀 on the root and workflow ownership
from a matching run recap, proof-bearing PR, or automation memory claim.
A bot reply, reaction, or memory entry alone is insufficient. Investigate
before replying, and read the thread for human updates. A root
listed in the
Reports section of a sweep
PR that is still open and that this run didn't open belongs to the run
working on that PR: don't react
or reply there, and leave it out of your self-check; just list it under
"Still open from earlier runs". If that PR has had no push in 24 hours,
its run has stopped: its reports are yours again. Of the remaining
workflow roots, those without ✅ or 🎫 come first in this run. A newer
human reply is context, not by itself a reason to respond: investigate the
claimed report and leave conversations already handled by people alone. A
root with 🎫 and our reply after its latest human message is already answered: you may still fix it, but post nothing there
until the fix merges. A
reply like "still broken" after a ✅ means the earlier fix failed. Find what
that fix changed and why it didn't hold before trying again.
- New reports: roots from the last 5 days. React and reply on the root
message's own
ts. A channel-history row whose thread_ts differs from its
ts is a reply that was also sent to the channel: use its thread_ts
parent instead. Read the thread for every root
that looks like a report. Open screenshots and attachments, since the error
text in a screenshot is often the whole diagnosis.
- Other sources. Unread or failing sources are reported as
unavailable, never as "nothing found".
- GitHub: open issues updated in the window
(
gh issue list --state open --search "updated:>=<date>"). Skip ones
someone else has offered to fix.
- Sentry (through its connector, or the local reader the invocation
names) and Agent-Native Analytics (
list-error-issues, then
get-error-issue): unresolved, recent, and repo-owned. Rank by users
affected. An error with a stack trace is already a reproduction lead.
2. Triage: lean toward fixing
Put each report in one bucket:
- Fix: anything objectively broken. This means errors, nothing happening
on click, lost or wrong data, regressions, slowness, jank, and visible
defects like clipped or overlapping text, unreadable contrast, or a broken
layout. A credible "nothing happens" counts as evidence.
- Build: a feature request or UX change carrying a maintainer's
:upvote: or :yes-party:.
- Needs a person (🎫): subjective product or UX changes no maintainer has
endorsed (add, move, hide, or restyle controls; "hard to find"), work that needs access or settings only
a person has, a provider outage, or a report you can't act on without one
missing fact. A bug you couldn't reproduce by reading code is still a Fix.
- Not actionable: praise, chatter, announcements, things a human already
answered, duplicates of something already in this run. These get no
reaction and no reply.
Issues from the error and health sources above go in the same buckets,
ranked with the Slack reports by people affected. They have no thread to react on,
so they appear only in the recap.
Claim Fix reports in order of people affected. Unfinished claims stay in
"Claimed reports" for the next run. Any Fix, Build, or Needs-a-person root you leave
unclaimed gets no reaction, only one line in the recap saying why, so
nothing is dropped silently. That covers every candidate your source helpers
return: each one ends the run either claimed or on a recap line with its
reason.
In scheduled and manual runs, record each root (channel and ts) under "Claimed
reports" in the feedback automation's memory.md, then add and verify 👀
before investigating. A record alone does not establish a claim: the root
must also have the verified 👀 from this workflow. Retain the record until
the report is resolved or a person takes over. If shared memory is unavailable,
do not claim new roots.
3. Fix as many as you can
- Group related reports so one cause gets one fix. Give each independent
group a fresh subagent on your own model and effort, with disjoint files,
or fix it in the main thread. Never hand a finished helper a new job; start
a fresh one. The main thread plans, reviews diffs, and integrates.
- Reproduce before you edit. Get the failure on screen first: a test
that fails, the action returning the wrong thing, a stack trace, or the
flow broken in a signed-in local app. Reading code is not an attempt:
write the report's steps as a failing test, or walk them in the signed-in
app. A broken setup isn't an attempt either: when a test can't load or an
install fails, fix the setup (install what's missing, or free space by
removing only this run's own build output) or
walk the steps in the signed-in app instead. Only after a real attempt fails does a report become 🎫, and its
recap line says what you ran. No reproduction means no code change.
- Check the history.
git log --since=30.days --oneline -- <files>: if
this surface was fixed before for the same symptom, that fix treated a
symptom. Find the shared cause (fix-at-the-boundary) instead of adding
one more patch, and look for the same pattern elsewhere.
- Prove it. The check has to fail with the fix's source changes put
back to
main and pass with them. A check that passes without your fix
doesn't test the bug: write one that does. Tests that read source text
never count. For a purely visual fix, before and after screenshots are
evidence, not automated proof: before merging, a human must open both and
confirm they show the reported change. Put the evidence under the report in
the PR's Reports section. A test-only change (test files, optional
.changeset/) needs only fix-proof: test-only.
- Two misses, then stop guessing. If two attempts don't turn the check
green, stop editing and capture the real failure first (stack, logs, the
reporter's actual data). If that doesn't settle it within about 30
minutes, it becomes 🎫 with one line on what you learned.
- Second opinion before the PR, every time. Give a fresh subagent on
your own model only the report text, the diff, and the proof, and ask: does
the check exercise what the reporter saw, is this the cause or a symptom,
and what edge case breaks it? Fix what it finds before you open the PR.
- Keep fixes small. Each report's fix goes in its own commit so a bad
one can be reverted alone. A fix that grows past about 300 lines, or into
a new subsystem (timeouts, cancellation, retries) the reporter didn't ask
for, isn't a sweep fix: ship the small part and 🎫 the rest. Match the
versions the workspace already pins; a sweep is not a dependency upgrade.
- Never tune agent instructions or prompts around one report's wording.
4. Ship
Put every fix in one PR, and open it once every claimed Fix report has a
fix or a failed attempt, so CI waits come after the fixing. Don't open one
PR per item. End the PR body with a
## Reports heading listing the link of every report the PR fixes: the
Slack thread, or the Sentry, Analytics, or GitHub issue. That list is the
only set of threads a later /ship may close out as fixed.
Wait for CI with one command that blocks until every check finishes, and
wait on it with the longest call your tool allows, not a short call you
repeat: every call re-sends your whole context.
Without a repo command for it, run
gh pr checks <number> --watch --interval 60 > /dev/null in one call bounded
by your tool's limit, then read gh pr checks <number> twice, a minute
apart: CI is done only when both reads list the same checks, at least one,
and none is pending. Otherwise wait again the same way and rerun any cancelled check; after
about two hours, stop and look at the PR yourself.
Fix each review round's findings in one batch. If a second round still finds
a problem in the same fix, take that fix out of the PR, remove its whole entry
from the PR's Reports section: the link and its fix-proof: and visual:
lines (close-out marks every listed report fixed, and a stray evidence line
counts toward the report above it). Then 🎫 its
report with what review found, and merge the rest. Close the PR only when nothing verified
is left in it.
Merge it the way this repo merges PRs. In a Factory workspace, that means
the workflow's merge step after its merge gate, never a direct merge.
A sweep's PR contains product fixes only. Don't edit this skill, add checker
scripts, or add bookkeeping files in it. If the run taught something, propose
a one-line lesson in the recap for a maintainer to accept or drop.
5. Close the loop
This step is the only place a claimed report gets its closing reply. Run it
after the merge for the threads in the PR's Reports section. If the merge
happened outside this run, the next sweep runs it: when you collect, list the
sweep PRs merged in the window (gh pr list --state merged --limit 100 --search "merged:>=<date>") and close out every report in their Reports sections
that still lacks its ✅, however old the report is.
Entries that aren't Slack threads get no Slack action: GitHub issues follow
the issue rule below, and Sentry and Analytics issues are only listed in the
recap.
Run it once per thread: if a reply in the thread already links this PR, just make sure ✅ is
there and move on.
Write only as the connected Slack profile, only in the feedback
channels, and in the reply format from the contract above. First re-read
the contract and this step from fresh origin/main (git fetch origin main && git show origin/main:.agents/skills/review-latest-feedback/SKILL.md): a
run that started hours ago may be holding older rules. Re-read each thread before
writing. If a maintainer has since added :mag: or a person has taken it over,
leave it. If a newer human reply says it's still broken, leave the 👀 for the
next sweep. Otherwise:
- Merged fix: add ✅ and reply that it's fixed, with the PR linked, and
will be on beta shortly. Only for reports whose
Reports entry carries a
proof (step 3). Without one, it's 🎫 and a reply that the fix is logged for a
person to check.
- Fix ready but not merged yet (for example CI is still running when the
run must end): reply that a fix (PR linked) is in review. Don't mention
beta yet. The next run adds ✅ once it's merged, with no second reply.
- Needs a person: add 🎫 and say in plain words what's known and what's
needed, without naming anyone ("thanks - logged for a product decision").
- Couldn't reproduce: add 🎫. If one small answer from the reporter would
unblock it and you couldn't find it yourself, ask for just that. Otherwise
say you couldn't reproduce it yet. Never ask
for anything already in the thread.
GitHub issues fixed by the merged PR get a one-line thank-you comment linking
the PR, and then get closed. Post it even when someone else opened the issue,
or the PR already closed it: reporters should be told.
Before ending, re-read each thread you touched and check:
- every 👀 from this run has an investigated disposition and, unless a person
has taken over, a reply plus ✅, 🎫, or an open fix PR listed under
Reports;
- every ✅ corresponds to a merged fix;
- no reply is technical or duplicated.
6. Recap
Keep the recap short, for the maintainer reading it:
## Feedback sweep - <date, Pacific>
Fixed and merged (N): <one line each, with Slack thread link> · PR <link>
Closed out from earlier runs (N): <Slack thread link> · PR <link>
Needs a person (N): <what's needed, who, what you tried>
Still open from earlier runs (N): <why>
Seen, not picked (N): <Slack thread link> - <one-line reason>
Roots: <n> seen, <n> claimed, <n> left
Sources unavailable: <list or "none">
Lesson (optional): <one line>
"Fixed and merged" is this run's PR only; reports you closed out for an
earlier run's merged PR go under "Closed out from earlier runs".
In an automation, append the same recap to its memory.md.
1---2name: review-latest-feedback-23description: >-4 Sweep recent feedback (the Slack feedback channels, GitHub issues, CI on5 main, Sentry, Analytics errors, chat run health, deploys), fix as many real6 bugs as possible, ship them in one PR, then close the loop on every Slack7 report with 👀/✅/🎫 and one short plain-English reply. Use for scheduled or8 manual feedback sweeps, usually followed by /ship.9user-invocable: true10scope: dev11metadata:12 source: https://skillmd.com/skills/builderio/review-latest-feedback-213 internal: true14---1516# Review Latest Feedback1718The job: find what's broken, fix as much of it as you can, ship it, and tell19each reporter in one friendly sentence what happened. A sweep is judged by20bugs fixed and merged, and by every claimed report getting a clear answer. It is21not judged by ledgers, receipts, or checker output.2223## The contract2425The detailed Slack reaction and reply rules are in26[slack-reaction-replies.md](references/slack-reaction-replies.md); read it before27marking, replying to, or closing any Slack report.2829Slack reactions on a report's root message mean exactly this:3031| Mark | Meaning | When to add |32| ---- | ----------------------------------------- | ------------------------------------------------------------------------------------------------ |33| 👀 | "I'm on this" | Before you investigate, and only on reports you will finish answering in this run |34| ✅ | "Fixed" | After the fix is merged to `main` (main deploys to beta automatically) |35| 🎫 | "Needs a person" | A product call, access or credentials, info from the reporter, or a fix you couldn't land |3637A maintainer is a Builder.io team member in the workspace who is not the38reporter and not a bot. Maintainers steer the sweep with reactions on a root:3940| A maintainer adds | Meaning |41| ----------------- | ----------------------------------------------------------------------------------------- |42| `:mag:` | Don't work on this; someone else will. Wins over everything below |43| `:yes-party:` | Definitely do this, even if it looks ambiguous or like a UX change. Build the smallest version that does what was asked |44| `:upvote:` | Same as `:yes-party:` for a feature request |45| 👀 by hand | They're working on it themselves; leave it (see "Open items first" for how to tell their 👀 from ours) |4647Reactions can't be removed through the Slack connector, so never add one you48might need to take back. Every 👀 you add ends the run with a reply, plus49either ✅ or 🎫, or a fix PR that is still open and lists the report (its50merge adds the ✅).5152Every claimed report gets **one** reply in its thread per outcome. The one exception is53the merged `✅` close-out after an in-review reply, which gets no second reply. Each reply must be:5455- **An answer first:** if they asked something ("is this expected?"),56 answer it in the first words ("no, that's a bug"), not with a status.57- **Short:** one sentence, about 25 words at most, for someone who doesn't58 read code.59- **About what they'll notice:** say what changes for them ("recordings no60 longer get stuck on Saving"), not how it works ("cleanup now waits for the61 transcript"). Leave out file, function, and service names, PR numbers,62 ticket IDs, CI, logs, runs, "repro", "verified", "scope", "sweep", status63 labels ("In progress:", "Skipped:", "Resolved elsewhere:", "Blocked on64 human owner:", "Open - no question:"), and any mention of this workflow.65 Never report your own progress ("unreproduced", "not traced yet",66 "remains open"); say what happens next instead.67- **Clear on what happens next:** "I'll ..." when this workflow acts. When it68 needs a person, never name one and never say "the team", "product", "the69 framework team", "the owner", or "someone": say only what's known ("I70 couldn't reproduce this yet", "logged for a product decision"), add 🎫, and71 record it as needing a person with the reason. Never @-mention anyone.72- **Not a to-do list for them:** look things up yourself first (the73 message's time and author, their account and recent activity, logs, the74 linked page or screenshot). Ask only when nothing else can unblock it, and75 then ask one small thing, in this one reply. Never send a list of76 questions, never ask them to test, retry, re-record, pull, reinstall, or77 gather logs, and never come back later asking for something you could have78 asked the first time. If it needs access you don't have (credentials, admin79 rights, account changes), say it's logged for someone with access and add80 🎫; never hand it to the reporter.81- **Plain, not preachy:** don't explain how the product works unless they82 asked, don't tell them what they should do, and skip apologies, hedging,83 "actually", "just", "simply", and "Great catch!!".84- **True:** "fixed" only for a merged fix, and "on beta shortly" only after85 the merge. Before that, the fix is "in review". Never "fixed and verified"86 on the strength of a local check.87- **Once:** never post the same reply twice, and never follow up with one88 that adds nothing new.89- Link the PR on the word "fix" (`<url|fix>`), never by number.90- End with the bold line `**This was sent from a bot**` on its own line,91 once.9293Don't reply at all to jokes, venting, banter, a message meant for a specific94teammate, or a thread a person is already handling. Once a person says they95have it, or asks the bot to stop, post nothing more in that thread. Before posting, reread the reply as the reporter: would they get it96in five seconds, know what happens next, and feel we did the legwork? Check97the draft before sending, not after: the first version is the one that98notifies them, so editing it afterwards doesn't undo it.99100Good (each is the first line; the footer goes on the line below it):101102- `thanks - the <https://github.com/BuilderIO/agent-native/pull/1234|fix> so the export keeps your column order is merged and will be on beta shortly.`103- `thanks - once this <https://github.com/BuilderIO/agent-native/pull/1234|fix> merges, the export will keep your column order; it's in review now.`104- `thanks - where that button should go is logged for a product decision.`105- `thanks - I couldn't find which deck this was; could you paste its link?`106107So a full reply looks like:108109```text110thanks - the <https://github.com/BuilderIO/agent-native/pull/1234|fix> so the export keeps your column order is merged and will be on beta shortly.111**This was sent from a bot**112```113114Real replies that missed, and what to send instead:115116| Sent | Instead |117| --- | --- |118| "Could you send the recording link, approximate time, and browser so we can trace whether the clip produced media before it tried to save?" | Find the recording from the reporter and message time first. If you still can't: "thanks - I couldn't find which recording this was; could you paste its link?" |119| "cleanup now waits for the transcript, and a fix is ready. It should be on beta shortly." (sent before the merge) | "thanks - recordings will keep their transcript once this <url\|fix> is merged; it's in review now." |120| "I've left moving it somewhere easier to find for product to decide." | "thanks - where the editor should live is logged for a product decision." |121| "Partially fixed - PR #7512 merged the project-instructions/context carryover fix", after she'd asked whether FullStory could be added for the whole org | Answer that question first: "yes - I'll add it for everyone" or "not yet - that's logged for a decision". |122| "All fixed and verified. Please try again!" plus instructions to pull main and reinstall | "thanks - this <url\|fix> is merged and will be on beta shortly." No homework. |123| More replies after Shawn wrote "bot please stop! I've got this all fixed and in flight" | Nothing. A person has it. |124| "Thanks for correcting me, Julia - I misread the replies. ... Open - no question: I don't have enough source evidence to claim a fix." | Nothing: the thread was a joke. |125| Asked for the app URL, what was clicked, and the time; then, in a second reply, for the time zone. | One reply, one question, only for what you can't look up. The message's own timestamp already says when. |126127## Boundaries128129- **Slack:** only `#product-agent-native-feedback` (`C0ATH3CCZT4`)130 and `#qa-agent-native` (`C0C4U4XRT6X`), a narrower set the invocation131 names, or a caller's list (as in `factory-run`). Never132 react or reply elsewhere. Reply only in a report thread this workflow133 claimed with 👀 and investigated; a bot reply alone isn't a claim.134 Never start a new channel message.135- **Leave a report alone** when:136 - a maintainer put `:mag:` or their own 👀 on it (table above);137 - someone in the thread asked a specific person to look, a teammate says138 they're handling it, or a maintainer asked for a human on it;139 - another person's 👀 sits on it and they've been active in the last 3140 days;141 - an earlier run's PR for it is still open. That PR's `/ship` closes the142 report out when it merges.143- **PRs:** push to, comment on, or merge only the PR this run opened. PRs from144 other sessions share the active GitHub login (`gh api user --jq .login`), so145 authorship proves nothing: a PR under that login may be another thread's146 work in flight, and pushing to it lands unreviewed commits on it. Never touch any other PR unless the invocation names that exact PR and147 action. That holds inside `/ship` too: its "Your PRs" means this run's PR.148- **One run, one PR.** Every sweep PR is authored by the active GitHub login, so the149 author check can't tell runs apart: an150 open PR with a `Reports` section that this run didn't open belongs to151 another run that may still be working on it. Don't push to, reply on, or152 merge it; list it under "Still open from earlier runs".153- **Goals end with the run.** If you set a Codex goal, scope it to this run:154 name its PR once you have one, and end it after step 6 ("merge PR #N,155 close its Reports, append the recap"). Never set an open-ended goal such as156 "review feedback" or "fix my open PRs". Goals resume after restarts,157 so an open-ended one keeps running into the next scheduled sweep and158 collides with it.159- Use the connected Slack integration for every Slack read and write. Confirm160 which profile is connected before the first write; every reply and reaction161 posts as that profile.162163## Dry run164165On "dry run", run every step but send nothing:166167- Record each reaction and the exact reply you'd post, linking the fix branch168 where the PR would go.169- Treat other runs' claims as unclaimed; honor a maintainer's `:mag:` and 👀.170- Publish one branch per fix group; skip PRs, merges, `/ship`, and comments.171- Skip the connected-profile check; use the state the invocation names.172173## 1. Collect (keep it under ~15 minutes)174175Work in a task-owned worktree on fresh `origin/main`. If you start in a shared176checkout, or the expected worktree is missing, create one177(`git worktree add <path> origin/main`) and carry on. That is never a reason178to stop.179180Window: roots posted in the last 5 days (or since the timestamp or permalink181the invocation gives), for new reports and open items alike. An older thread182is in the window too when we have already replied in it and a person has183replied since the window began: a channel read only shows roots, so search for184recent thread replies (`in:<#channel> is:thread after:<date>`) to find them.185Roots in `memory.md` under "Claimed reports", "Claimed, not yet answered",186or "Must handle next run" are always in the window. Other older threads are left as they are, except reports listed under187`Reports` in a sweep PR opened or merged in that window: those always get188their close-out.189190Give each source below its own helper on the cheapest model (Luna in Codex,191Haiku in Claude Code), and close it as soon as it reports. A helper gathers;192you triage. The Slack helper returns every root a person posted in the window with no ✅, 🎫, or `:mag:`,193and every root with a person's reply newer than ours, one line each (link,194author, first line). It never filters, ranks, or drops one: a new report has195no reaction and no thread yet.196197- **Read the channels.** Use `slack_read_channel` with198 `response_format: detailed` (paginate) back 5 days. Its output shows199 reaction counts but not who added them, so call `slack_get_reactions` on any200 root showing `eyes`, `white_check_mark`, `ticket`, `mag`, `yes-party`, or201 `upvote`. Avoid `hasmy:`; run the202 [backstop](references/slack-reaction-replies.md#backstop-for-unclaimed-roots).203- **Open items first.** Verify the connected profile's 👀 on the root and workflow ownership204 from a matching run recap, proof-bearing PR, or automation memory claim.205 A bot reply, reaction, or memory entry alone is insufficient. Investigate206 before replying, and read the thread for human updates. A root207 listed in the `Reports` section of a sweep208 PR that is still open and that this run didn't open belongs to the run209 working on that PR: don't react210 or reply there, and leave it out of your self-check; just list it under211 "Still open from earlier runs". If that PR has had no push in 24 hours,212 its run has stopped: its reports are yours again. Of the remaining213 workflow roots, those without ✅ or 🎫 come first in this run. A newer214 human reply is context, not by itself a reason to respond: investigate the215 claimed report and leave conversations already handled by people alone. A216 root with 🎫 and our reply after its latest human message is already answered: you may still fix it, but post nothing there217 until the fix merges. A218 reply like "still broken" after a ✅ means the earlier fix failed. Find what219 that fix changed and why it didn't hold before trying again.220- **New reports:** roots from the last 5 days. React and reply on the root221 message's own `ts`. A channel-history row whose `thread_ts` differs from its222 `ts` is a reply that was also sent to the channel: use its `thread_ts`223 parent instead. Read the thread for every root224 that looks like a report. Open screenshots and attachments, since the error225 text in a screenshot is often the whole diagnosis.226- **Other sources.** Unread or failing sources are reported as227 **unavailable**, never as "nothing found".228 - GitHub: open issues updated in the window229 (`gh issue list --state open --search "updated:>=<date>"`). Skip ones230 someone else has offered to fix.231 - Sentry (through its connector, or the local reader the invocation232 names) and Agent-Native Analytics (`list-error-issues`, then233 `get-error-issue`): unresolved, recent, and repo-owned. Rank by users234 affected. An error with a stack trace is already a reproduction lead.235236## 2. Triage: lean toward fixing237238Put each report in one bucket:239240- **Fix:** anything objectively broken. This means errors, nothing happening241 on click, lost or wrong data, regressions, slowness, jank, and visible242 defects like clipped or overlapping text, unreadable contrast, or a broken243 layout. A credible "nothing happens" counts as evidence.244- **Build:** a feature request or UX change carrying a maintainer's245 `:upvote:` or `:yes-party:`.246- **Needs a person (🎫):** subjective product or UX changes no maintainer has247 endorsed (add, move, hide, or restyle controls; "hard to find"), work that needs access or settings only248 a person has, a provider outage, or a report you can't act on without one249 missing fact. A bug you couldn't reproduce by reading code is still a Fix.250- **Not actionable:** praise, chatter, announcements, things a human already251 answered, duplicates of something already in this run. These get no252 reaction and no reply.253254Issues from the error and health sources above go in the same buckets,255ranked with the Slack reports by people affected. They have no thread to react on,256so they appear only in the recap.257258Claim Fix reports in order of people affected. Unfinished claims stay in259"Claimed reports" for the next run. Any Fix, Build, or Needs-a-person root you leave260unclaimed gets no reaction, only one line in the recap saying why, so261nothing is dropped silently. That covers every candidate your source helpers262return: each one ends the run either claimed or on a recap line with its263reason.264265In scheduled and manual runs, record each root (channel and ts) under "Claimed266reports" in the feedback automation's `memory.md`, then add and verify 👀267before investigating. A record alone does not establish a claim: the root268must also have the verified 👀 from this workflow. Retain the record until269the report is resolved or a person takes over. If shared memory is unavailable,270do not claim new roots.271272## 3. Fix as many as you can273274- Group related reports so one cause gets one fix. Give each independent275 group a fresh subagent on your own model and effort, with disjoint files,276 or fix it in the main thread. Never hand a finished helper a new job; start277 a fresh one. The main thread plans, reviews diffs, and integrates.278- **Reproduce before you edit.** Get the failure on screen first: a test279 that fails, the action returning the wrong thing, a stack trace, or the280 flow broken in a signed-in local app. Reading code is not an attempt:281 write the report's steps as a failing test, or walk them in the signed-in282 app. A broken setup isn't an attempt either: when a test can't load or an283 install fails, fix the setup (install what's missing, or free space by284 removing only this run's own build output) or285 walk the steps in the signed-in app instead. Only after a real attempt fails does a report become 🎫, and its286 recap line says what you ran. No reproduction means no code change.287- **Check the history.** `git log --since=30.days --oneline -- <files>`: if288 this surface was fixed before for the same symptom, that fix treated a289 symptom. Find the shared cause (`fix-at-the-boundary`) instead of adding290 one more patch, and look for the same pattern elsewhere.291- **Prove it.** The check has to fail with the fix's source changes put292 back to `main` and pass with them. A check that passes without your fix293 doesn't test the bug: write one that does. Tests that read source text294 never count. For a purely visual fix, before and after screenshots are295 evidence, not automated proof: before merging, a human must open both and296 confirm they show the reported change. Put the evidence under the report in297 the PR's `Reports` section. A test-only change (test files, optional298 `.changeset/`) needs only `fix-proof: test-only`.299- **Two misses, then stop guessing.** If two attempts don't turn the check300 green, stop editing and capture the real failure first (stack, logs, the301 reporter's actual data). If that doesn't settle it within about 30302 minutes, it becomes 🎫 with one line on what you learned.303- **Second opinion before the PR, every time.** Give a fresh subagent on304 your own model only the report text, the diff, and the proof, and ask: does305 the check exercise what the reporter saw, is this the cause or a symptom,306 and what edge case breaks it? Fix what it finds before you open the PR.307- **Keep fixes small.** Each report's fix goes in its own commit so a bad308 one can be reverted alone. A fix that grows past about 300 lines, or into309 a new subsystem (timeouts, cancellation, retries) the reporter didn't ask310 for, isn't a sweep fix: ship the small part and 🎫 the rest. Match the311 versions the workspace already pins; a sweep is not a dependency upgrade.312- Never tune agent instructions or prompts around one report's wording.313314## 4. Ship315316Put every fix in one PR, and open it once every claimed Fix report has a317fix or a failed attempt, so CI waits come after the fixing. Don't open one318PR per item. End the PR body with a319`## Reports` heading listing the link of every report the PR fixes: the320Slack thread, or the Sentry, Analytics, or GitHub issue. That list is the321only set of threads a later `/ship` may close out as fixed.322323Wait for CI with one command that blocks until every check finishes, and324wait on it with the longest call your tool allows, not a short call you325repeat: every call re-sends your whole context.326Without a repo command for it, run327`gh pr checks <number> --watch --interval 60 > /dev/null` in one call bounded328by your tool's limit, then read `gh pr checks <number>` twice, a minute329apart: CI is done only when both reads list the same checks, at least one,330and none is pending. Otherwise wait again the same way and rerun any cancelled check; after331about two hours, stop and look at the PR yourself.332333Fix each review round's findings in one batch. If a second round still finds334a problem in the same fix, take that fix out of the PR, remove its whole entry335from the PR's `Reports` section: the link and its `fix-proof:` and `visual:`336lines (close-out marks every listed report fixed, and a stray evidence line337counts toward the report above it). Then 🎫 its338report with what review found, and merge the rest. Close the PR only when nothing verified339is left in it.340341Merge it the way this repo merges PRs. In a Factory workspace, that means342the workflow's merge step after its merge gate, never a direct merge.343344A sweep's PR contains product fixes only. Don't edit this skill, add checker345scripts, or add bookkeeping files in it. If the run taught something, propose346a one-line lesson in the recap for a maintainer to accept or drop.347348## 5. Close the loop349350This step is the only place a claimed report gets its closing reply. Run it351after the merge for the threads in the PR's `Reports` section. If the merge352happened outside this run, the next sweep runs it: when you collect, list the353sweep PRs merged in the window (`gh pr list --state merged --limit 100 --search354"merged:>=<date>"`) and close out every report in their `Reports` sections355that still lacks its ✅, however old the report is.356Entries that aren't Slack threads get no Slack action: GitHub issues follow357the issue rule below, and Sentry and Analytics issues are only listed in the358recap.359Run it once per thread: if a reply in the thread already links this PR, just make sure ✅ is360there and move on.361362Write only as the connected Slack profile, only in the feedback363channels, and in the reply format from the contract above. First re-read364the contract and this step from fresh `origin/main` (`git fetch origin main365&& git show origin/main:.agents/skills/review-latest-feedback/SKILL.md`): a366run that started hours ago may be holding older rules. Re-read each thread before367writing. If a maintainer has since added `:mag:` or a person has taken it over,368leave it. If a newer human reply says it's still broken, leave the 👀 for the369next sweep. Otherwise:370371- **Merged fix:** add ✅ and reply that it's fixed, with the PR linked, and372 will be on beta shortly. Only for reports whose `Reports` entry carries a373 proof (step 3). Without one, it's 🎫 and a reply that the fix is logged for a374 person to check.375- **Fix ready but not merged yet** (for example CI is still running when the376 run must end): reply that a fix (PR linked) is in review. Don't mention377 beta yet. The next run adds ✅ once it's merged, with no second reply.378- **Needs a person:** add 🎫 and say in plain words what's known and what's379 needed, without naming anyone ("thanks - logged for a product decision").380- **Couldn't reproduce:** add 🎫. If one small answer from the reporter would381 unblock it and you couldn't find it yourself, ask for just that. Otherwise382 say you couldn't reproduce it yet. Never ask383 for anything already in the thread.384385GitHub issues fixed by the merged PR get a one-line thank-you comment linking386the PR, and then get closed. Post it even when someone else opened the issue,387or the PR already closed it: reporters should be told.388389Before ending, re-read each thread you touched and check:390391- every 👀 from this run has an investigated disposition and, unless a person392 has taken over, a reply plus ✅, 🎫, or an open fix PR listed under `Reports`;393- every ✅ corresponds to a merged fix;394- no reply is technical or duplicated.395396## 6. Recap397398Keep the recap short, for the maintainer reading it:399400```md401## Feedback sweep - <date, Pacific>402Fixed and merged (N): <one line each, with Slack thread link> · PR <link>403Closed out from earlier runs (N): <Slack thread link> · PR <link>404Needs a person (N): <what's needed, who, what you tried>405Still open from earlier runs (N): <why>406Seen, not picked (N): <Slack thread link> - <one-line reason>407Roots: <n> seen, <n> claimed, <n> left408Sources unavailable: <list or "none">409Lesson (optional): <one line>410```411412"Fixed and merged" is this run's PR only; reports you closed out for an413earlier run's merged PR go under "Closed out from earlier runs".414415In an automation, append the same recap to its `memory.md`.