skills.rest
vTRKA
vTRKACOMMUNITY
Explore all skills by this author →
GitHub

receiving-code-review

Evaluate code review findings into evidence-based accept, reject, clarify, defer, or escalate decisions.

Updated Apr 27, 2026
Search Tags:#code review#security#verification#PR feedback#triage#evidence-based fixes#resolution record
One-click install
npx skills add https://github.com/vTRKA/supervibe --skill receiving-code-review-vtrka
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: receiving-code-review
Source: https://github.com/vTRKA/supervibe/tree/main/skills/receiving-code-review
Command: npx skills add https://github.com/vTRKA/supervibe --skill receiving-code-review-vtrka

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It converts incoming code review feedback into a rigorous, evidence-backed resolution plan before any edits happen, preventing performative agreement and reducing the risk of accepting incorrect or unsafe suggestions.

Core Features & Use Cases

  • Finding triage before changes: normalize reviewer feedback into stable finding IDs with severity, file/line impact, evidence status, and blocker tracking.
  • Decision-by-evidence workflow: accept, accept-with-change, reject-with-evidence, clarify, defer, or escalate—grounded in code/spec/test/verification output rather than intent.
  • Verification and traceable outcomes: require targeted verification for accepted fixes, record tradeoffs and residual risk, and produce a final response mapping every finding to an outcome.

Quick Start

When you receive PR or reviewer comments, tell your AI: “Use receiving-code-review to evaluate each finding with evidence before implementing any suggestion, then produce a per-finding resolution record with verification.”

Frequently Asked Questions about receiving-code-review

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

FAQPage Schema
How do I triage PR review feedback before implementing changes?▼

Triage PR review feedback by normalizing comments into stable finding IDs with severity, file/line impact, evidence status, and blocker tracking before making any code changes.

When should I reject code review findings instead of accepting them?▼

Reject code review findings when you lack supporting code, spec, test, or verification output evidence. Use reject-with-evidence or clarify decisions to avoid performative agreement and prevent unsafe edits.

What is an evidence-based code review resolution workflow?▼

An evidence-based code review resolution workflow evaluates each finding with technical rigor, requiring verification outputs for accepted fixes and mapping reviewer concerns to concrete outcomes and residual risks.

How do I resolve security and release-readiness findings in a pull request?▼

Resolve security and release-readiness findings by categorizing them into valid issues, ambiguities, optional suggestions, or out-of-scope work, then applying accept, reject, clarify, defer, or escalate decisions.

Can I defer or escalate code review comments that are out of scope?▼

Yes, you can defer or escalate code review comments that are out of scope. The workflow supports deciding to accept, accept-with-change, reject-with-evidence, clarify, defer, or escalate based on evidence.

Related Skills

Explore More Software Engineering Skills→
nadyshalabynadyshalaby
3

review-triage

Convert batches of reviewer feedback into a structured per-finding decision table.

Community
Advanced
conn-castleconn-castle
9

resolve-findings

Verify audit findings and document which issues require fixes.

Official
Advanced
projectedanxprojectedanx
1

oss-forensics

Analyze GitHub repositories for supply chain attacks using git, API, and logs.

Community
Advanced
OniReimuOniReimu
26

paper-reviewer

Generate structured, evidence-based peer reviews for academic manuscripts.

Community
Advanced