specdo-receive-code-review

Name: specdo-receive-code-review
Availability: InStock
Author: MoonCoder

Validate review feedback and route SpecDo workflow decisions.

Updated Aug 27, 2026

Search Tags:#automation #workflow #governance #code-review #review-feedback #wrapper

Ready to run

npx skills add https://github.com/MoonCoder-HAPPY/SpecDo --skill specdo-receive-code-review

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: specdo-receive-code-review
Source: https://github.com/MoonCoder-HAPPY/SpecDo/tree/main/specdo-receive-code-review
Command: npx skills add https://github.com/MoonCoder-HAPPY/SpecDo --skill specdo-receive-code-review

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates processing of concrete review feedback to drive SpecDo workflow decisions. It enforces the prerequisite of a complete active apply payload and ensures feedback is actionable before gating to the next step.

Core Features & Use Cases

Validate complete apply context: require task_scope, handoff_payload, gate_history, and invoked_from to be present; if missing, route to specdo-apply with needs_apply_context.
Evaluate concrete feedback: ensure feedback names a file, behavior, missing evidence, risk, or failing condition.
Route outcomes: accepted_unapplied, accepted, rejected, failure_exposed, or lifecycle_reassessment_required, and append gate_history entries accordingly.

Quick Start

Provide concrete review feedback to trigger this wrapper and advance the lifecycle.

Frequently Asked Questions about specdo-receive-code-review

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

FAQPage Schema

How do I automate code-review feedback processing for workflow routing?▼

Automate code-review feedback processing by validating concrete feedback against an active apply payload to determine the next workflow step. The system checks for complete context and routes outcomes to apply, verification, debugging, or rework based on the feedback content.

What makes code-review feedback actionable for automated workflow decisions?▼

Code-review feedback is actionable when it names a specific file, behavior, missing evidence, risk, or failing condition. The system validates these elements before gating the workflow to ensure feedback drives meaningful routing decisions.

How do I validate apply context before processing review feedback?▼

Validate apply context by requiring task_scope, handoff_payload, gate_history, and invoked_from to be present. If any prerequisite is missing, the system routes to specdo-apply with a needs_apply_context flag to gather the required information.

What routing outcomes can code-review feedback trigger in a workflow?▼

Code-review feedback triggers routing outcomes including accepted_unapplied, accepted, rejected, failure_exposed, or lifecycle_reassessment_required. Each outcome appends gate_history entries to guide subsequent workflow decisions.

When do I need lifecycle reassessment during code-review processing?▼

Lifecycle reassessment is needed when review feedback exposes failures or requires rethinking the current approach. The system produces a lifecycle_reassessment_required outcome to signal that the workflow must re-evaluate its direction.

Can I process review feedback without an active apply payload?▼

Processing review feedback requires an active apply payload with complete context. Without it, the system cannot validate feedback and will route to specdo-apply to establish the necessary task_scope, handoff_payload, and gate_history.