Menu
Create a GitHub issue from user feedback with safe context and simple labels. Never implement.
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
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.
| name | feedback |
| description | Create a GitHub issue from user feedback with safe context and simple labels. Never implement. |
Create the source GitHub issue and stop. Do not implement. Do not split into tickets.
Apply exactly one category when possible:
bugenhancementApply exactly one state:
needs-triage — clear enough for triageneeds-info — clarification is neededGrill now, defer, or skip?
needs-info.needs-triage.## Summary
## Observed
## Expected
## Context
- Route/panel:
- Package/plugin:
- Branch/SHA:
- Environment:
## Artifacts
## Redaction
## Acceptance
## Proof Ideas
- Exact command:
- Screenshot/demo:
- Manual steps:
- Waiver if proof is not possible:
## Open Questions
## Next
Suggested next step: `/triage #<issue>` or `/plan #<issue>`.