メニュー
Triage GitHub issues through a label-based state machine with interactive grilling sessions. Use when user wants to triage issues, review incoming bugs or feature requests, prepare issues for an AFK agent, or manage issue workflow.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Implement, port, or sign off Starshine optimizer passes with the repo-standard TDD, registry, Binaryen semantic parity, performance, validity, and documentation workflow. Use when working on pass creation, pass porting, pass parity, pass fuzz compare failures, optimizer registry wiring, preset changes, or pass signoff.
Commit current work using Starshine's commit policy. Use when the user asks to commit, create commits, save changes to git history, or prepare a commit from the current worktree.
Create a continuation thread with default thread parameters and a comprehensive handoff of the current task. Use when the user says "/handoff", asks to hand off the current work, continue in another thread, or wants a fresh thread with full context.
Ultra-compressed communication mode. Cuts token usage ~75% by dropping filler, articles, and pleasantries while keeping full technical accuracy. Use when user says "caveman mode", "talk like caveman", "use caveman", "less tokens", "be brief", or invokes /caveman.
Generate multiple radically different interface designs for a module using parallel sub-agents. Use when user wants to design an API, explore interface options, compare module shapes, or mentions "design it twice".
Grilling session that challenges your plan against the existing domain model, sharpens terminology, and updates documentation (CONTEXT.md, ADRs) inline as decisions crystallise. Use when user wants to stress-test a plan against their project's language and documented decisions.
| name | github-triage |
| description | Triage GitHub issues through a label-based state machine with interactive grilling sessions. Use when user wants to triage issues, review incoming bugs or feature requests, prepare issues for an AFK agent, or manage issue workflow. |
Triage issues in the current repo using a label-based state machine.
Any GitHub comment created during triage must start with:
> *This was generated by AI during triage.*
Every issue should have exactly one category label and one state label.
Category labels:
bugenhancementState labels:
needs-triageneeds-infoready-for-agentready-for-humanwontfixIf labels conflict, stop and resolve the conflict first.
.out-of-scope/*.md for matches.ready-for-agent, write a durable agent brief.wontfix, record it in .out-of-scope/.See AGENT-BRIEF.md and OUT-OF-SCOPE.md.