receive-feedback
Process external code review feedback with technical rigor. Use when receiving feedback from another LLM, human reviewer, or CI tool. Verifies claims before implementing, tracks disposition.
When & Why to Use This Skill
This Claude skill automates the systematic processing of external code review feedback with technical rigor. By prioritizing a verification-first discipline, it helps developers evaluate suggestions from human reviewers, CI tools, or other LLMs, ensuring that only technically sound changes are implemented while maintaining a clear audit trail of all disposition decisions.
Use Cases
- Automated PR Feedback Processing: Systematically verify and implement comments from GitHub or GitLab pull requests using tool-based validation to ensure technical correctness.
- AI-to-AI Collaboration: Evaluate and filter code suggestions provided by other LLM sessions to prevent the introduction of hallucinations or suboptimal patterns.
- CI/CD Pipeline Triage: Handling feedback from linters and automated testing tools by applying a decision matrix to determine whether to implement, reject with evidence, or defer changes.
- Pair Programming Refinement: Managing real-time suggestions during collaborative coding sessions by verifying claims against the codebase before execution, prioritizing technical accuracy over social compliance.
| name | receive-feedback |
|---|---|
| description | Process external code review feedback with technical rigor. Use when receiving feedback from another LLM, human reviewer, or CI tool. Verifies claims before implementing, tracks disposition. |
Receive Feedback
Overview
Process code review feedback with verification-first discipline. No performative agreement. Technical correctness over social comfort.
Quick Reference
┌─────────────┐ ┌──────────────┐ ┌─────────────┐
│ VERIFY │ ──▶ │ EVALUATE │ ──▶ │ EXECUTE │
│ (tool-based)│ │ (decision │ │ (implement/ │
│ │ │ matrix) │ │ reject/ │
└─────────────┘ └──────────────┘ │ defer) │
└─────────────┘
Core Principle
Verify before implementing. Ask before assuming.
When To Use
- Receiving code review from another LLM session
- Processing PR review comments
- Evaluating CI/linter feedback
- Handling suggestions from pair programming
Workflow
For each feedback item:
- Verify - Use tools to check if feedback is technically valid
- Evaluate - Apply decision matrix to determine action
- Execute - Implement, reject with evidence, or defer
Files
VERIFICATION.md- Tool-based verification workflowEVALUATION.md- Decision matrix and rulesRESPONSE.md- Structured output formatTRACKING.md- Logging disposition to CSVreferences/skill-integration.md- Using with code-review skills