full-code-review

Reviews rsvelte pull requests through phased multi-agent code review with interactive fixes.

218|11|Updated Jan 4, 2026
One-click install
npx skills add https://github.com/baseballyama/rsvelte --skill full-code-review-baseballyama
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: full-code-review
Source: https://github.com/baseballyama/rsvelte/tree/main/.claude/skills/full-code-review
Command: npx skills add https://github.com/baseballyama/rsvelte --skill full-code-review-baseballyama

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve? Reviewing changes to a Rust port of the Svelte 5 compiler requires verifying behavioral parity with the official JavaScript implementation, hot-path performance, memory safety, and test coverage, which is error-prone when done manually in a single pass. ## Core Features & Use Cases - Phased Review Workflow: Walks through WHY validation, architecture review, AST/foundational type review, chunked implementation review, and final test execution, confirming with the user at each phase. - Multi-Agent Chunked Review: Splits the diff into review chunks via a planning script and runs up to eight specialized review agents (official-implementation parity, compiler implementation, performance, tests, security, simplification, CodeRabbit, Codex) per chunk, iterating until zero findings. - Use Case: Before submitting a PR that modifies the parser in crates/rsvelte_core, run the review to compare logic against submodules/svelte, catch unwrap() calls on production paths, and verify benchmark numbers with bench.sh. ## Quick Start Ask the assistant to run a full code review on the current branch or a specific PR number before submitting it.

Frequently Asked Questions about full-code-review

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

FAQPage Schema
How do I run a full code review on a pull request before submitting?▼

Invoke the skill with a request like "/full-code-review" or "review this PR". It determines the base branch, classifies changed files, then walks through WHY validation, design review, AST review, chunked implementation review, and final tests, asking for your approval at each phase.

How does the review verify parity with the official Svelte compiler?▼

A dedicated agent compares each changed Rust file against its counterpart in submodules/svelte/packages/svelte/src/compiler, checking algorithm order, output bytes, error codes, and naming. Behavioral differences are flagged as Critical findings with references to the official source.

What tools and commands does the review workflow require?▼

It uses git for diffs, the GitHub CLI (gh) for PR metadata and CI monitoring, Node.js for the chunk-planning script, and cargo fmt, clippy, and cargo test --release for validation. CodeRabbit and Codex agents run only if installed.

How are large pull requests split for review?▼

The plan-review-chunks.mjs script groups changed files by category (parse, analyze, transform, error, napi, tests, infra, docs) and splits them into chunks of at most 500 lines or 10 files, respecting directory boundaries. AST and submodule files are excluded from chunking.

What are the limitations of this review skill?▼

It is specific to the rsvelte repository structure and assumes paths like crates/rsvelte_core and submodules/svelte exist. Files outside known categories fall into an 'other' bucket requiring manual discussion, and review iterations are capped with a prompt after five rounds per agent.