Fix the feedback in specific Slack threads or a named Slack scope and answer each reporter in-thread. Use when the user points at particular Slack feedback and says "address this feedback", "fix these and reply", or links threads. For a full sweep of the feedback channels use review-latest-feedback.
96%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
Low
Low-risk findings worth noting
Triage, fix, ship, and answer the Slack threads the user pointed at, in one
pass. This is review-latest-feedback aimed at a specific set of threads
instead of the whole sweep. That skill owns the Slack contract: the 👀 / ✅ / 🎫
reactions, the one-sentence reply and its wording, which channels are fair
game, the "leave it alone" rules, and maintainer reactions such as :upvote:. Read it first and
follow it. This file adds only what is specific to working a given thread.
Use the connected Slack integration for every read and write, and confirm which profile is connected before the first write. Never drive Slack through a browser or computer use.
address-feedback, concurrent-agents, and verifying-changes. Re-read
dirty files and keep peer work intact; never reset, stash, or overwrite it.Apply the decision gate before reacting or editing, using the buckets in
review-latest-feedback:
:upvote: on a feature request means build the
smallest version that does what was asked; no second sign-off needed.Pick the fix altitude using address-feedback: smallest owning seam for one
report, the shared primitive for a repeated failure, and never a global agent
rule from one data point.
Once a thread is in scope, add 👀 before investigating, one thread at a time, and only if you'll finish answering it in this run. If the reaction fails, resolve that before going on.
review-latest-feedback, or @agent-native, and check it
hasn't already been answered or resolved.Group independent fixes across subagents with disjoint files, reproduce where
you reasonably can, fix, and verify as verifying-changes describes (a test
that fails before and passes after, or the flow working in the running app).
Timebox one item to about 30 minutes; if it doesn't yield, it becomes 🎫 with a
line on what you learned. Put the fixes in one PR and run /ship through the
merge, with every fixed thread's Slack link in the PR body's Reports
section. Only the PR this run opened gets pushed, merged, or commented on.
Run review-latest-feedback step 5 for every thread you put 👀 on. That
step owns the replies, reactions, and skip rules. Its no-duplicate check
covers the Reports threads /ship already closed out after the merge.
Then re-read each thread you touched and confirm the reply landed under the right parent. If a participant replies after you post, re-read the whole thread before deciding what to do next.
If the user says earlier replies were too technical, edit every reply from this run, not just the latest example.
Briefly: threads fixed (with links), threads needing a person and who, questions asked, anything you couldn't verify, and the PR link.
review-latest-feedback (Slack contract), address-feedback (classification
and fix altitude), concurrent-agents, verifying-changes.
BuilderIO/agent-native
cf9ff10
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.