skills.rest
Threat-Vector-Security
Threat-Vector-SecurityOFFICIAL
Explore all skills by this author →
WebsiteGitHub

receiving-code-review

Evaluate code-review feedback for technical accuracy before implementing changes.

11|3|Updated Feb 24, 2026
Search Tags:#validation#code-review#pull-request#engineering-process#senior-engineer#qa-feedback
One-click install
npx skills add https://github.com/Threat-Vector-Security/guardian-agent --skill receiving-code-review-threat-vector-security
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: receiving-code-review
Source: https://github.com/Threat-Vector-Security/guardian-agent/tree/main/skills/receiving-code-review
Command: npx skills add https://github.com/Threat-Vector-Security/guardian-agent --skill receiving-code-review-threat-vector-security

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Evaluate feedback technically before implementing it. Do not perform agreement. Do not batch changes blindly.

Core Features & Use Cases

  • Read and restate ambiguous feedback to ensure mutual understanding.
  • Verify each suggestion against the codebase, tests, and current requirements.
  • Implement changes incrementally with re-testing and explicit pushback when constraints are violated.

Quick Start

Clarify ambiguous feedback first, then implement changes incrementally with verifiable tests.

Frequently Asked Questions about receiving-code-review

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

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

Verify code review feedback by evaluating each suggestion against the codebase, tests, and current requirements. Restate ambiguous feedback first to ensure mutual understanding, then implement changes incrementally with re-testing.

How do I handle ambiguous pull request comments without blindly agreeing?▼

Handle ambiguous pull request comments by restating the feedback explicitly before editing. Do not perform agreement; instead, read the comment, clarify constraints, and push back when suggestions violate project requirements.

What is the best way to implement QA feedback across software projects?▼

The best way to implement QA feedback is to enforce step-by-step verification and incremental changes. Evaluate each point technically against requirements, clarify ambiguities, and avoid batching changes blindly.

When should I push back on reviewer suggestions?▼

Push back on reviewer suggestions when they violate existing constraints, tests, or current requirements. Technical evaluation ensures you only implement changes that pass verification rather than performing automatic agreement.

Can I batch code review changes blindly to save time?▼

No, do not batch code review changes blindly. You must evaluate each suggestion technically for accuracy, implement changes incrementally, and perform explicit re-testing to ensure the edits do not violate constraints.

Related Skills

Explore More Software Engineering Skills→
LazyNinja435LazyNinja435
1

receiving-code-review

Evaluate and implement code review feedback with verification and pushback protocols.

Community
Intermediate
mvillmowmvillmow
18

gh-create-pr-linked

Create a GitHub pull request linked to a specified issue.

Community
Basic
dmedina-devdmedina-dev
1

verification-before-completion

Run a verification gate before declaring development tasks complete.

Community
Intermediate
ybbms777ybbms777
1

setup

Automate review agent selection for compound-engineering projects using ce:review.

Community
Basic