القائمة
The final gatekeeper for quality. Use after a feature implementation is finished to ensure OSS standards, performance, and architectural purity.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements, and design before implementation.
Use when you have a written implementation plan (from lg-plan-writer) to execute with review checkpoints and educational validation.
Helps students bootstrap a new Liquid Galaxy project by forking the starter kit and configuring standard parameters (2D/3D, screens, orientation).
Leverage AI (Nano Banana/Imagen) to generate high-quality game sprites and integrate them with real-time background removal for Liquid Galaxy demos.
Use when you have a spec or requirements for a multi-step task, before touching code. Creates a detailed, educational implementation plan for Liquid Galaxy projects.
The "Finale" of the project. A TV-show style quiz with 5 questions to evaluate the student's learning outcomes and technical understanding.
| name | Liquid Galaxy Code Reviewer |
| description | The final gatekeeper for quality. Use after a feature implementation is finished to ensure OSS standards, performance, and architectural purity. |
This is the fifth step in the 6-stage pipeline: Init -> Brainstorm -> Plan -> Execute -> Review -> Quiz (Finale). Its goal is to simulate a professional Open Source code review, ensuring the code is not just "working," but "excellent."
Announce at start: "I'm starting a professional Code Review for the [Feature Name] implementation."
Review the entire feature set for:
utils.js?You MUST run and verify the results of the following project tools:
npm run lint. There should be zero errors.npm run check-types. All JSDoc type-casts must be accurate.npm run test. All unit tests must pass.npm run coverage. New logic should have at least 80% coverage to ensure maintainability.disposing of geometries and materials?docs/ file explain how to use this new feature?Write the review results to docs/reviews/YYYY-MM-DD-<feature>-review.md.
Template:
# Code Review: [Feature Name]
## 🟢 The Good
- [List strengths, e.g., "Excellent use of Server-Authoritative physics."]
## 🛠 Tooling & Quality Status
- **Lint**: [PASS/FAIL]
- **Types**: [PASS/FAIL]
- **Tests**: [PASS/FAIL]
- **Coverage**: [X]% (Target: 80%)
## 🟡 Required Refactors (Gated)
- [List items the student MUST fix before 'merging'.]
- **Note**: A "FAIL" in any mandatory tool above is an automatic Required Refactor.
## 🔵 Best Practice Suggestions
- [List minor improvements for the future.]
## Final Verdict: [APPROVED / REVISIONS NEEDED]
*(A feature can only be APPROVED if all 4 Tools are in PASS state)*
If REVISIONS NEEDED, hand back to the Plan Writer or Executer to fix the issues. Do not consider the feature "Complete" until the review is APPROVED.
Once APPROVED:
chore: final polish after code review.