code-reviewer

Orchestrates multi-layer code reviews for NetEase Mod projects by coordinating specialized review sub-skills.

Updated Apr 11, 2026
One-click install
npx skills add https://github.com/Coral5644/NekansModPack --skill code-reviewer-coral5644
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: code-reviewer
Source: https://github.com/Coral5644/NekansModPack/tree/main/.cursor/skills/code-reviewer
Command: npx skills add https://github.com/Coral5644/NekansModPack --skill code-reviewer-coral5644

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Reviewing NetEase Mod code involves many dimensions—Python 2.7 compatibility, encoding safety, API correctness, UI bindings, RPC communication, configuration management, and performance—and checking them all manually is error-prone and inconsistent. This Skill acts as a central review orchestrator that classifies each change, dispatches the right specialized review sub-skills in the correct order, and merges their findings into one unified report. ## Core Features & Use Cases - Layered Review Pipeline: Runs blocking checks first (Py2.7 syntax, encoding, API verification), then design and convention review, then domain-specific checks (UI, RPC, config), then simplification and performance, and finally runtime instrumentation when static analysis is inconclusive. - Adaptive Review Levels: Automatically selects quick, standard, or deep review based on change size, or honors an explicitly requested level. - Unified Severity Report: Produces a consolidated report with 🔴/🟠/🟡/🟢 severity tiers, per-skill issue counts, and a pass/fail gate (🔴 = 0 and 🟠 ≤ 2). - Use Case: After finishing a feature that touches JSON UI and RPC endpoints, ask for a deep review; the orchestrator will invoke the syntax, clean-code, UI-binding, and RPC sub-skills in parallel, deduplicate findings, and return a single actionable report. ## Quick Start Review my current changes with a deep code review and give me a consolidated severity-ranked report.

Frequently Asked Questions about code-reviewer

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

FAQPage Schema
How do I run a comprehensive code review on NetEase Mod code?▼

Invoke the code-reviewer skill, which classifies your change type and automatically dispatches the right specialized sub-skills. It runs blocking checks first, then design, domain, and improvement layers, and returns one consolidated severity-ranked report.

What review levels are available for code review automation?▼

Three levels exist: quick for changes of three files or fewer, standard for completed features or routine reviews, and deep for architecture changes, large refactors, or security audits. Deep review is the default unless you specify otherwise.

Does this review process support Python 2.7 compatibility checks?▼

Yes, Python 2.7 compatibility is a mandatory blocking-layer check for every review. It flags f-strings, function annotations, bare super() calls, and raise-from syntax, and blocks further review layers when fatal incompatibilities are found.

Can the review verify NetEase API and event signatures?▼

Yes, when API, event, or enum usage is uncertain, the review triggers a dedicated API research sub-skill to verify official signatures and availability. If static verification remains inconclusive, it escalates to in-game runtime instrumentation.

When should I use a single linter instead of an orchestrated review?▼

A single linter suits isolated style or syntax checks on small scripts. The orchestrated review is better for cross-cutting changes involving UI bindings, RPC communication, configuration, or performance, where multiple specialized checks must be coordinated and merged.