Menu
Classify existing issues or PRs with the Boring state model and record the next action.
Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.
Drive one ready artifact through implementation, proof, review, and owner handoff.
Review the named UI scenario or emit one bounded improvement packet.
Teach a boring-ui child app how to enable Google signup with @hachej/boring-core. Use when the user asks for Google auth, Google OAuth, social signup, or how to turn on Google sign-in/sign-up in a child app.
Ask which Boring skill or workflow fits your situation. A router over the local Boring skills.
Run an extremely strict maintainability review for abstraction quality, giant files, spaghetti-condition growth, and code-judo simplification opportunities.
Route a request to the right Boring v2 workflow skill without doing the work.
Baseado na classificação ocupacional SOC
| name | triage |
| description | Classify existing issues or PRs with the Boring state model and record the next action. |
| disable-model-invocation | true |
Classify; do not implement. Use the labels, blocker vocabulary, and transitions in
docs/kanzen/boring-loop.md.
State: <state> Category: <category>
Blocked by: <first blocker>
Next: /skill:<route> <target>
Proof expected: <command | demo | manual step | waiver>
Human request: <ask_user id or comment URL, if any>
Notes: <only material context>
Use ask_user for specific human questions; otherwise post them on the issue/PR.