菜单
Review exported feedback JSON from the in-app feedback panel, evaluate each pending entry, and selectively file GitHub issues via gh CLI. Use when the user says "review feedback", "triage feedback", or "file feedback issues".
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Generate game audio (music, voices, sound effects) via ElevenLabs.
Generate a project briefing: worktree status, open checkboxes, recent commits. Modes: summary (default), report, verify, current, worktrees. Period: 1h, 6h, 24h, 2d, 7d.
Safe commit workflow with optional scope hint. Inventories all changes, classifies related vs. unrelated files, traces dependencies, protects other agents' work, and optionally pushes or lands worktree commits. Usage: /commit [pr] [scope] [push|land]
Lightweight task dispatcher for ad-hoc work: documentation, examples, refactoring, content updates. Supports scheduling with every/now/next/stop. Usage: /do <description> [worktree] [push] [pr] [every SCHEDULE] [now] | stop | next.
Audit and fix documentation gaps: block library panel entries, example models, getting-started guides, block library, presentations, README updates. Also handles newsletter entries (/doc newsletter). Use when the user asks to "write a newsletter entry", "add to the newsletter", or "update the newsletter". Usage: /doc [blocks|examples|newsletter|<description>]
Draft a high-quality plan through iterative adversarial review. Multiple rounds of research, drafting, review, devil's advocate, and refinement until the plan converges. Output is a plan file ready for /run-plan. Usage: /draft-plan [output FILE] [rounds N] <description...>
| name | review-feedback |
| description | Review exported feedback JSON from the in-app feedback panel, evaluate each pending entry, and selectively file GitHub issues via gh CLI. Use when the user says "review feedback", "triage feedback", or "file feedback issues". |
Review exported feedback JSON from the in-app feedback panel, evaluate each pending entry, and selectively file GitHub issues.
User says: "review feedback", "triage feedback", "file feedback issues",
or invokes /review-feedback.
The exported feedback.json file should be in the repo root (or the user
will specify the path). This file is exported from the app via
Feedback Panel > History > Export JSON.
Read the feedback JSON file:
cat feedback.json
Or run the summary helper first:
node scripts/review-feedback.js feedback.json
For each pending entry, evaluate:
gh issue list --search "keyword" --state open
bug, enhancement, ui, question)Present a summary table to the user showing your recommendations:
| # | Title | Type | Severity | Recommendation | Reason |
|---|---|---|---|---|---|
| 1 | ... | bug | high | File | Clear repro |
| 2 | ... | feature | low | Dismiss | Too vague |
Wait for user approval before filing anything.
File approved entries as GitHub issues:
gh issue create --title "Title here" --body "$(cat <<'EOF'
**Type:** bug
**Severity:** high
**Reported:** 2026-03-11
Description here.
### Context
- Model: ModelName
- Blocks: 12
- Sim state: idle
- Solver: ode45
EOF
)" --label "bug"
Update the JSON file with filed status and issue numbers:
status: "filed" and githubIssue: "#NNN" for filed entriesstatus: "dismissed" for dismissed entriesTell the user they can re-import the updated JSON in the app via the browser console:
// In browser console:
const store = new (await import('./src/io/FeedbackStore.js')).FeedbackStore();
store.importJSON(await (await fetch('feedback.json')).text());
| Feedback type | GitHub label |
|---|---|
| bug | bug |
| ui | bug, ui |
| feature | enhancement |
| question | question |