receiving-code-review
Receiving Code Review
Treat review feedback as technical input to verify, not as a script to perform.
Context
receiving-code-review is the author-side companion to reviewer-side code-review. Its job is to stop two failure modes:
- blind implementation of feedback that breaks the real codebase
- performative agreement that sounds collaborative but skips technical verification
In Prodcraft, review reception must preserve brownfield constraints, existing contracts, release boundaries, and upstream decisions. External feedback is useful input, not automatic truth.
Inputs
- review-report -- The reviewer comments, blocking issues, questions, and requested changes.
- source-code -- The current implementation and surrounding codebase reality that the feedback must fit.
- test-suite -- The existing safety net used to verify each accepted change.
More from yknothing/prodcraft
system-design
Use when reviewed requirements or specifications are ready and the team must decide high-level architecture, component boundaries, integration seams, or brownfield coexistence strategy before API design, technology selection, or task planning.
6ci-cd
Use when a reviewed implementation slice needs an automated build, test, and deployment pipeline, especially when brownfield rollback, release-boundary checks, contract/integration gates, and staged delivery must be explicit before shipping.
6intake
The mandatory gateway for all new engineering work. Triage and route new products, apps, features, migrations, tech-debt, or any 'not sure where to start' request to the correct lifecycle path. Use before starting design or implementation. Do not use for ongoing tasks, specific debugging, or PR reviews.
6feature-development
Use when a reviewed task slice has tests or acceptance targets and the team must turn it into a small, mergeable implementation increment without expanding scope, breaking contracts, or hiding release-boundary risk.
6monitoring-observability
Use when a live service or newly delivered release needs actionable telemetry, dashboards, and alerts that expose real user-impactful boundaries, especially when brownfield coexistence rules, unsupported-flow safety, rollback health, or queue/backfill behavior must be visible before incidents escalate.
6incident-response
Use when a live production issue needs coordinated containment, severity triage, stakeholder communication, and evidence capture, especially when a recent release, brownfield coexistence rules, rollback decisions, or unresolved contract boundaries must be handled before root-cause work.
6