Categorize, fix, and reply to PR review comments and QA ticket feedback.
npx skills add https://github.com/sandsower/beislid --skill review-response-sandsower
Please help me install this Agent Skill. Skill: review-response Source: https://github.com/sandsower/beislid/tree/main/skills/review-response Command: npx skills add https://github.com/sandsower/beislid --skill review-response-sandsower
pr_review_source, QA/ticket comments via ticket_source, or strictly pasted feedback, then normalizes everything into a single categorized queue. - Categorized fixing with policy gates: Classifies each item as clear fix, needs investigation, pushback, already addressed, out-of-scope, or clarification needed, and evaluates action policy before every write, commit, push, or reply. - Safe reply posting: Posts Fixed in <sha> replies, pushback reasoning, and review re-requests only through configured update commands using temp-file JSON payloads, never ad-hoc gh api calls. - Use Case: A reviewer leaves five comments on your PR and QA adds two ticket comments. Run this Skill to fetch both sources, fix the clear issues, draft pushback for one incorrect comment, run pre-PR gates, push, and post replies to each original thread. ## Quick Start Ask the agent to respond to the review comments on my current pull request and the QA feedback on my ticket.High-intent search queries and answers about installing and using this skill.
Run the review-response flow on your branch: it detects the current PR, fetches unresolved review threads through your configured pr_review_source command, categorizes each comment, applies clear fixes, runs gates, pushes, and posts Fixed-in replies through pr_review_update.
Choose the combined mode when prompted. The Skill fetches PR review threads and ticket comments, normalizes them into one queue so duplicate requests are fixed once, and routes each reply back to its original source.
The Skill stops automated retrieval and asks you to paste the review feedback using a strict prompt. It never falls back to ad-hoc gh api, gh pr view --comments, or GraphQL queries for fetching or posting review data.
No. Every write, commit, push, reply, and review re-request goes through an action-policy check; ask-classified actions require explicit approval. A fast path exists only when all feedback is clear, sources are non-manual, and the diff is small.
Do not use it to start new ticket work, create pull requests, or review someone else's PR. Use kickoff, ready-for-review, or pr-patrol for those tasks instead.
ak-eytherFetch and organize GitHub pull request review comments and inline threads.
cogpyMerge prepared GitHub pull requests via squash after validation.
mitchellfyiMonitor GitHub pull requests for CI failures and unresolved review feedback.
mvillmowReplies to GitHub PR inline review comments via the comment replies API.