菜单
Use for /feedback: create one enriched GitHub issue with safe context, lean labels, first plan, and queued or grill-blocked state.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
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 | boring-feedback |
| description | Use for /feedback: create one enriched GitHub issue with safe context, lean labels, first plan, and queued or grill-blocked state. |
Goal: /feedback creates the GitHub issue. Never implement.
Issue shape: follow
docs/kanzen/procedures/well-documented-issue.md.
| Step | Output |
|---|---|
| Capture | report, route, panel/plugin, selected item, branch/SHA, app/browser context, redacted errors, optional screenshot |
| Redact | preview before publish; no secrets, cookies, auth headers, private data, unrelated transcripts, or host-local paths |
| Issue | create the well-documented issue |
| First plan | likely area, acceptance criteria, flag/abstraction guess, proof path |
| Labels | source:feedback, one state:*, one phase:*, track:owner |
bug, ui, accessibility, package:*, plugin:*, gate:*.feedback, repo/item scope, capture context.unavailable; never invent fixed session fields.If unclear, ask whether to grill now, defer, or skip.
| Choice | Result |
|---|---|
| grill now | use grill-me before final routing |
| defer | create issue as state:blocked phase:grill; record gate clarity in the body |
| skip/clear | create issue as state:queued phase:triage; record gate triage in the body |
Use ask-user for deferred questions so the session appears as pending in boring-ui.
For attachments, keep the GitHub attachment or safe filename in the issue; do not publish the original host-local path.