receiving-code-review

Name: receiving-code-review
Availability: InStock
Author: axiomantic

Route received code-review feedback to the replacement skill.

8|5|Updated Dec 30, 2025

Search Tags:#automation #feedback #routing #handoff #deprecated #code-review

Ready to run

npx skills add https://github.com/axiomantic/spellbook --skill receiving-code-review-axiomantic

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: receiving-code-review
Source: https://github.com/axiomantic/spellbook/tree/main/skills/receiving-code-review
Command: npx skills add https://github.com/axiomantic/spellbook --skill receiving-code-review-axiomantic

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill routes received code-review feedback to the replacement, avoiding legacy behavior and ensuring consistency with the code-review --feedback workflow.

Core Features & Use Cases

Immediate routing: on load, forwards all provided context to the replacement skill.
No independent execution: the skill does not process feedback itself, it delegates to replacement.

Quick Start

On load, immediately route all provided context to the replacement via /code-review --feedback.

Frequently Asked Questions about receiving-code-review

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

FAQPage Schema

How do I route code-review feedback to avoid legacy behavior?▼

To route code-review feedback and avoid legacy behavior, this skill immediately forwards all provided context to the replacement workflow on load. It delegates the feedback processing entirely instead of executing it independently.

What is the best way to handle post-review feedback handoffs in software engineering?▼

For post-review feedback handoffs, the skill enforces immediate routing to the replacement workflow. It forwards all context without performing any standalone feedback processing, ensuring a clean transition.

Why does this skill perform no standalone feedback processing?▼

This skill performs no standalone feedback processing because it is designed to strictly enforce immediate routing. By delegating all context to the replacement workflow, it guarantees consistency and avoids legacy behavior.

When do I need to use a routing skill for code-review feedback?▼

You need a routing skill for code-review feedback when dealing with post-review scenarios and handoffs where legacy behavior must be avoided. It ensures immediate delegation to the replacement workflow upon load.

Does the receiving-code-review skill process feedback independently?▼

No, the receiving-code-review skill does not process feedback independently. It immediately routes all provided context to the replacement workflow to ensure consistency and avoid legacy behavior.