Menu
Use for branch, diff, sensitive file, commit, push, tag, and release safety.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Pre/Post execution validation + Phase Gate enforcement — ป้องกันการข้าม step, auto-validate output, ให้คะแนน quality score
สแกน code ใน Scaffold/ ด้วย 53 security rules (6 หมวด) — secrets, permissions, injection, AI-specific, config, dependencies — ก่อน deploy หรือหลัง Dev report
Coordinate PM/Dev/QA agents แบบ Pipeline Pattern — auto-route งานตาม role, ส่งต่ออัตโนมัติเมื่อ status เปลี่ยน, track progress ทุก handoff
Create color-coded teaching scripts / presenter talking-point documents (.md) that serve as a "live reading book" for speakers. The output is a markdown file where each color tells the presenter what to do: blue = speak this line, red = pronunciation guide, dark blue = slide header, black = stage direction & audience engagement, yellow box = terminology. Use this skill whenever the user mentions: teaching script, talking points, presenter script, key talking point, speaker notes, lecture script, training script, presentation script, สคริปต์การสอน, สคริปต์วิทยากร, คำพูดที่ต้องอ่าน, หนังสือสำหรับพูด, or any request to create a document that guides a speaker through a slide deck with exact words to say, pronunciation help, and stage directions. Also trigger when the user uploads a PowerPoint (.pptx) and asks to write a script, narration, or talking points for it.
Use for QA evidence, release readiness, rollback review, and close-out decisions.
Use for build completion evidence, code review readiness, and ready-for-QA checks.
| name | pmo-git-safety |
| description | Use for branch, diff, sensitive file, commit, push, tag, and release safety. |
Keep git operations reviewable, intentional, and safe.
Use before commit, push, tag, branch changes, release publication, or when sensitive files may be present.
Current branch, git status, diff summary, validation output, human approval state, and git/release permissions from pmo-config/policy.json.
Read git metadata and changed files needed for review. Do not inspect denied secret files.
Use pmo-config/policy.json for git mutation and production release permission requirements. Lite, Standard, and Strict all require human confirmation for commit/push/tag; push requires explicit per-push confirmation.
Return branch, account/remote if requested, changed files, test result, and pending human actions.
Commit is local only after per-round diff approval. Push/PR/merge require final explicit approval. Production release approval cannot be automated.
powershell -NoProfile -ExecutionPolicy Bypass -File scripts/run-all-checks.ps1
Do not use destructive git commands, force push, bypass permissions, approve production release, push without explicit per-push confirmation, or commit unrelated user changes.
Working tree changes are intentional, tests are green, no sensitive files are included, and human approval is recorded.
