code-quest-review

Review Code Quest pull requests for protocol, handler, and Zod alignment.

11|2|Updated Feb 5, 2026
One-click install
npx skills add https://github.com/recca0120/code-quest --skill code-quest-review
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-quest-review
Source: https://github.com/recca0120/code-quest/tree/main/.claude/skills/code-quest-review
Command: npx skills add https://github.com/recca0120/code-quest --skill code-quest-review

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams avoid subtle breakages when Code Quest changes land, such as mismatched event names, misplaced Zod schemas, or inconsistent server/summoner/client handler semantics that can silently desync the protocol pipeline.

Core Features & Use Cases

  • Project-specific code review checklist for Code Quest conventions across shared, server, summoner, and client layers.
  • Protocol and event-name alignment checks ensuring socket-events definitions, REQUEST_MAPPINGS, adapter control transformations, and client/server emit/on wiring stay consistent.
  • Zod and isolatedDeclarations governance verifying schema placement, avoiding deprecated Zod v4 patterns, and preventing incorrect or redundant type assertions.
  • Handler and core semantics verification covering middleware wrapping rules, Channel mutability constraints, and ChannelEmitter dispatch/broadcast semantics.
  • Summoner adapter and FakeSummoner test pattern checks ensuring request mappings are complete and tests validate the full pipeline instead of spying internals.
  • UI/compatibility/style guardrails including React Compiler compatibility, icon facade conventions, and token-first UI design principles.

Quick Start

Use the code-quest-review skill while reviewing a Code Quest PR to verify protocol/handler/Zod alignment and ensure recent changes match project conventions.

Frequently Asked Questions about code-quest-review

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

FAQPage Schema
How do I prevent protocol drift between server, client, and adapter handlers during code changes?

To prevent protocol drift, validate event-name mapping, verify REQUEST_MAPPINGS coverage, and check cross-package alignment between server emit/on wiring and the summoner adapter. This ensures handler middleware semantics stay consistent across shared definitions.

What is the correct placement for Zod schemas under isolatedDeclarations?

Correct Zod schema placement under isolatedDeclarations requires verifying schema locations, avoiding deprecated Zod v4 patterns, and preventing incorrect or redundant type assertions. This governance keeps shared type definitions synchronized across packages.

How do I validate FakeSummoner test patterns for full pipeline coverage?

Validate FakeSummoner test patterns by ensuring tests exercise the full request mapping pipeline instead of spying on internal functions. Complete REQUEST_MAPPINGS and transformControlRequest coverage verifies the summoner adapter behaves correctly end to end.

Does the Code Quest review process enforce React Compiler compatibility and UI conventions?

The Code Quest review process enforces React Compiler compatibility, icon facade conventions, and token-first UI design principles. It also checks import/order rules to maintain UI layer consistency and prevent styling or compilation regressions.

Why do Channel and ChannelEmitter dispatch semantics need verification during code review?

Channel and ChannelEmitter dispatch semantics need verification to prevent silent desync errors caused by mutability constraint violations. Checking broadcast and dispatch behavior ensures the event pipeline maintains consistent state across server and client handlers.