菜单
Prepare and publish a compliant BrainRot pull request by checking scope, metadata, documentation, tests, commit conventions, branch safety, push state, and PR content. Use when the user asks to commit, push, publish, open, or create a pull request for completed work.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Inspect, triage, implement, test, and reply to unresolved BrainRot pull request review comments while preserving exact model ownership for game files. Use for human, Copilot, or automated PR feedback and requested changes.
Create, improve, or fix BrainRot game implementations while enforcing exact AI model ownership, standalone-file architecture, quality requirements, desktop-first gameplay, metadata maintenance, and documentation updates. Use for any change under public/games or any new game/version request.
Build, substantially revise, or visually review BrainRot Three.js games. Use for any game implementation that imports Three.js or creates a THREE.WebGLRenderer, including art direction, authored 3D forms, local GLB/image assets, rendering budgets, test hooks, diagnostics, and active-play visual verification.
Validate BrainRot repository changes with process-safe, change-scoped local checks while leaving the complete lint, build, and Playwright gate to required pull request CI. Use after implementation, before committing or opening a PR, or when diagnosing test and build failures.
Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, artifacts, posters, or applications (examples include websites, landing pages, dashboards, React components, HTML/CSS layouts, or when styling/beautifying any web UI). Generates creative, polished code and UI design that avoids generic AI aesthetics.
Prepare a BrainRot repository work session on a new task branch created from the latest remote main branch. Use when starting a new task, initializing a fresh coding session, or when the user asks to create a branch before implementation.
| name | create-pull-request |
| description | Prepare and publish a compliant BrainRot pull request by checking scope, metadata, documentation, tests, commit conventions, branch safety, push state, and PR content. Use when the user asks to commit, push, publish, open, or create a pull request for completed work. |
Publish when all of these are true:
start-session; it is not a default, detached, or unrelated branch.npm run update-metadata evidence with line counts and feature flags checked against the implementation.verify-changes path passed for the current diff. Reuse that evidence; rerun it only if relevant files changed or the result is stale or ambiguous.Stop rather than silently retrofitting a branch after work has accumulated. Never commit or push task changes directly to a default branch.
Review the staged diff once before committing.
Start the commit subject with an actual Unicode Gitmoji matching the primary change.
Include the existing required trailer exactly:
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Push the current branch with upstream tracking. Never force-push unless the user explicitly authorizes it.
Prefer the harness's connected GitHub tools to create the PR; fall back to gh pr create when needed.
Start the PR title with an actual Unicode Gitmoji. Include a concise summary and the exact local validation commands and outcomes in the body.
Confirm the required pull request workflow started. Do not wait for completion unless the user requested it, the task changes CI/test infrastructure, or a failure needs diagnosis.
Return the PR URL and current check state. The required aggregate CI check must pass before merge.
PR review handling is separate. Do not wait or poll for reviews unless the user asks; apply address-pr-review-comments when feedback arrives.