boonsook-review
为不直接改代码的评审者与提示作者提供流程指导。
用于分析、审查及为实现团队撰写实现提示与独立验证结果。
面向 Boonsook POS V5 的审查与分析流程，用来做代码/交付品的审查、为实现团队写实现提示（prompt）、以及独立验证发布结果。适合你不亲自改代码，而是要 review commit、验收部署、或检查库存/数据是否正常的场景。重点是不替实现团队提交代码，而是做分析、撰写实现指示并独立验证结果，常在泰语或英文请求下触发。
▸ 展开 SKILL.md 英文原文
Analyst / reviewer / prompt-author workflow for the Boonsook POS V5 project (Thai POS PWA — vanilla JS + Supabase + Cloudflare Pages, owner gangboo). Use this whenever the job is to ANALYZE, REVIEW, AUTHOR an implement-team prompt, or VERIFY shipped work — i.e. you are NOT editing/committing the code yourself (a separate implement team / Codex / another Claude Code session does that). Trigger generously on Thai or English requests such as "ช่วยวิเคราะห์/ตรวจงาน", "รีวิว/ตรวจ Phase นี้ / commit นี้ / build นี้", "เขียน prompt ให้ทีม implement / ให้ผมส่งอีกทีม", "verify deploy/build", "ตรวจสอบแอป มีอะไรผิดปกติ / มีบั๊กค้างมั้ย", "ระบบสต็อก/คลัง/ข้อมูลถูกต้องไหม", or designing/speccing a feature for the team to build — even when the user never says "skill", "review", or names a file. Do NOT use it when the owner explicitly asks you to implement / edit / commit the change yourself (that is implement mode). Reply in Thai; technical terms in English.
帮我安装这个 skill：https://raw.githubusercontent.com/boonsook/boonsook-pos-v5/main/.claude/skills/boonsook-review/SKILL.mdcurl -fsSL "https://raw.githubusercontent.com/boonsook/boonsook-pos-v5/main/.claude/skills/boonsook-review/SKILL.md"# Boonsook POS V5 — Analyst / Reviewer / Prompt-Author workflow This skill is for the mode where **you do not edit or commit code yourself**. A separate implement team (Codex or another Claude Code session) does the implementation and pushes. Your job is to **analyze, review, author implement-team prompts, and independently verify results**. Owner = `gangboo`. Reply in Thai; keep technical terms in English; cite `file:line`. The single most important habit, learned the hard way on this project: **verify against the source of truth, never assume — not from memory, not from a report.** Wrong assumptions about schema, EOL, row counts, or "it's already configured" have repeatedly almost caused