receiving-code-review-extras

What problem does it solve?

This Skill solves the problem of conflicting code review feedback, mismatches between review findings and status boards, and red team/audit findings that either contradict each other or would violate existing user constraints when converted into action plans. It eliminates the guesswork of determining which findings are valid and ensures remediation plans respect hard user rules.

Core Features & Use Cases

• Conflict Adjudication: Uses the actual codebase as the authoritative source to resolve disagreements between reviews or between a review and a status board, separating stale findings from real issues.
• Constraint-Compliant Planning: Converts external findings (code reviews, red team reports, audits) into action plans that adhere to standing user constraints, explicitly flagging any suggested fixes that would violate existing rules.
• Use Case: For example, if a code review claims a security gate is broken but the status board shows it was fixed, or a red team finding suggests a fix that violates a user's no-re-run policy, this skill resolves the conflict and creates a compliant plan.

Quick Start

Use the receiving-code-review-extras skill to adjudicate conflicting code review findings and create a constraint-compliant action plan for the latest audit results.