菜单
Scan a milestone (or the backlog / open issues) for low-effort, high-value work, triage genuine quick wins from disguised epics, and recommend what to do next. Use when the user asks for "quick wins", "low-hanging fruit", "what's easy in milestone X", or "anything I can knock out".
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | quickwins |
| description | Scan a milestone (or the backlog / open issues) for low-effort, high-value work, triage genuine quick wins from disguised epics, and recommend what to do next. Use when the user asks for "quick wins", "low-hanging fruit", "what's easy in milestone X", or "anything I can knock out". |
Find work that is small to do and worth doing, separate it from work that only looks small, and recommend a next step.
gh issue list --milestone "<name>" --state open --limit 50. (Milestone titles, not numbers, for this flag; gh api repos/:owner/:repo/milestones if you need to find the title.)gh issue view <n>, and --comments when there's discussion) before judging. A one-line title hides both trivial fixes and design epics.A quick win is: contained to a few files, low blast radius, clear acceptance, and lands green without a migration or design debate. Examples: a CI/config addition, a focused test file, a docs fix, a small self-contained feature.
Not a quick win (flag these, don't start them):
When something looks small but isn't, say so in one line and explain why — that's as useful as the win itself.
create-pr skill — branch, gates, Co-Authored-By + 🤖 footers, Closes #N, report mergeable, don't merge.A tight triage: what's quick (and why), what isn't (and why), and your recommendation. No exhaustive survey of options you won't pursue.
Cut a Surface release the way this repo does it — prepare the version-bump PR (Cargo version, Cargo.lock, doc pins, CHANGELOG) off a release/X.Y.Z branch, then after it merges, tag vX.Y.Z to trigger the build/npm-publish/docs-sync workflow. Use when the user asks to "cut a release", "release X.Y.Z", "prepare a release", or "tag the release".
Open a pull request for the current work following this repo's conventions — branch off main, run the gates, commit with the Co-Authored-By footer, push, and open a PR with the 🤖 footer and a Closes
Explain something in plain, non-technical language — "explain like I'm 5". Use when the user asks to ELI5, "explain simply", "in plain English", "what did we just do", or wants a jargon-free version of a PR, diff, commit, code, error, or concept.