flux-receive-review

Evaluate review feedback against the codebase and tests before implementing changes.

7|1|Updated Feb 21, 2026

Search Tags:#workflow #verification #review #engineering #code-review #pull-request

Ready to run

npx skills add https://github.com/Nairon-AI/flux --skill flux-receive-review

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: flux-receive-review
Source: https://github.com/Nairon-AI/flux/tree/main/skills/flux-receive-review
Command: npx skills add https://github.com/Nairon-AI/flux --skill flux-receive-review

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Feedback from humans, RepoPrompt, Codex, and PR comments often arrives as noisy or ambiguous prompts. This skill provides a disciplined workflow to interpret feedback and determine the exact changes to apply, reducing miscommunication and rework.

Core Features & Use Cases

Read the full set of feedback and restate the requirement in clear technical terms.
Verify proposed changes against the current codebase and tests before acting.
Decide whether the feedback is correct, unclear, or context-missing, and push back with technical reasoning when needed.

Quick Start

Just provide a specific PR or issue and have the assistant evaluate the feedback and return a verified change plan.

Frequently Asked Questions about flux-receive-review

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

FAQPage Schema

How do I turn pull request review feedback into verified code changes?▼

To turn pull request review feedback into verified code changes, evaluate each instruction against your current codebase and tests, then implement the action or push back with technical reasoning. This ensures feedback is interpreted correctly and changes are justified.

What is the best way to handle ambiguous PR comments from automated code review tools?▼

Handling ambiguous PR comments from automated code review tools requires restating the feedback in clear technical terms and verifying the proposed changes against existing tests before acting. This disciplined workflow reduces miscommunication and prevents unnecessary rework.

How do I verify code review instructions against my current codebase before applying them?▼

Verify code review instructions by reading the full feedback, restating requirements technically, and checking proposed changes against your current codebase and tests. Decide if the feedback is correct, unclear, or missing context before implementing or pushing back.

Can I push back on GitHub review comments with technical reasoning?▼

Yes, you can push back on GitHub review comments with technical reasoning when feedback is unclear or missing context. Evaluate the instruction against your tests, determine if it is correct, and reply with a justified technical explanation for your decision.

Why does interpreting review feedback incorrectly cause rework in software engineering?▼

Interpreting review feedback incorrectly causes rework because noisy or ambiguous prompts lead to misapplied code changes. A deterministic workflow that restates requirements and verifies changes against the codebase before implementation reduces this miscommunication.

Do I need existing tests to evaluate and translate code review feedback accurately?▼

Existing tests are needed to evaluate and translate code review feedback accurately because the workflow verifies proposed changes against the current codebase and tests before acting. This ensures feedback is interpreted correctly and changes are justified.