Evaluate review feedback against the codebase and tests before implementing changes.
npx skills add https://github.com/Nairon-AI/flux --skill flux-receive-review
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
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.
Just provide a specific PR or issue and have the assistant evaluate the feedback and return a verified change plan.
High-intent search queries and answers about installing and using this skill.
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.
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.
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.
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.
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.
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.
evalstateExtract and analyze writing suggestions from GitHub PR review comments.
mamu7211Fetch, categorize, and resolve GitHub pull request review threads via API.
dopsonbrValidate implementation work against plan specifications with Codex CLI reviews.
dmedina-devVerify code review feedback accuracy before implementing changes.
