receive-feedback

Verify external code review feedback before implementing, rejecting, or deferring changes.

75|9|Updated Dec 21, 2025
One-click install
npx skills add https://github.com/anderskev/beagle --skill receive-feedback
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: receive-feedback
Source: https://github.com/anderskev/beagle/tree/main/skills/receive-feedback
Command: npx skills add https://github.com/anderskev/beagle --skill receive-feedback

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

It provides a disciplined process for handling external feedback (from LLMs, reviewers, or CI) by verifying claims before acting and tracking dispositions.

Core Features & Use Cases

  • Verify Before Act: Apply a formal evaluation matrix to feedback items.
  • Structured Responses: Produce standardized, actionable replies.
  • Tracking & Backlog: Record dispositions for audit and follow-up.

Quick Start

For each feedback item, verify with tooling, evaluate against rules, then execute a fix, defer, or reject with evidence.

Frequently Asked Questions about receive-feedback

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I systematically verify code review feedback before implementing changes?

Verification-first workflow processes external feedback—from LLMs, reviewers, or CI—by applying a formal evaluation matrix to each item. You verify claims with tooling, evaluate against rules, then execute a fix, defer, or reject with evidence, ensuring only valid changes proceed.

What's the best way to track and document feedback dispositions across code reviews?

Structure feedback responses with standardized disposition tracking that records whether each item was implemented, deferred, or rejected with supporting evidence. This creates an audit trail for follow-up and backlog management across multiple feedback sources.

Can I use this workflow with feedback from LLM sessions, human reviewers, and CI outputs together?

Yes. The verification-first discipline applies uniformly to feedback from LLMs, pair-programming suggestions, PR comments, and CI outputs. A single decision matrix evaluates all sources, enabling traceable execution and structured reporting across mixed feedback workflows.

How do I reject feedback with evidence rather than dismissing it?

Evaluate each feedback item against your decision matrix using tooling verification. For rejections, document the evidence—test results, architectural constraints, or performance data—alongside the disposition so decisions remain traceable and defensible.

What happens when feedback conflicts with existing code or architecture?

The evaluation matrix surfaces conflicts during verification. You can defer the change with documented reasoning, reject with architectural evidence, or implement with refactoring. Structured reporting preserves the conflict context for later resolution.