メニュー
Choose one concrete next action from the user's Markdown idea directory. Use when the user invokes $idea-next or asks what to do next, what to work on now, which idea/PR/project to advance, or how to break choice paralysis using previously captured ideas.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Use when the user wants to inspect, classify, add, remove, replace, synchronize, or verify labels on a GitHub pull request; require evidence-backed current impact for bug, security, severity, and priority classifications, preserve unrelated labels, plan changes before applying them, and use the bundled REST-based helper for authorized mutations
Use when the user wants a maintainer-quality review of a GitHub PR, actionable findings, blocker or closure recommendations, or explicitly authorized COMMENT-only GitHub feedback; gate deep review on supported-path reachability and evidenced net value, report close/no-merge directly for unreachable or valueless changes, never approve PRs, and use pr-worktree for isolated local checkout
Use when the user explicitly wants to modify an existing GitHub PR as a maintainer and push focused fixes to its head branch; establish the confirmed issue, protected contract, minimal change cone, and verification evidence first; use pr-worktree so the current workspace is not disturbed
Safely rebase an existing GitHub pull request branch onto the latest base branch, resolve conflicts while preserving the PR's intent, rerun focused verification, and optionally update the remote PR branch. Use when the user asks to rebase, sync, refresh, or bring a PR up to date with main or another base branch, especially before merge or after the base branch changed.
Rewrite and polish Chinese technical writing through selective, comparative edits and relevant references, including author-approved samples, before/after pairs, voice profiles, factual sources, and platform examples. Use when the user asks to rewrite, polish, 润色, 改写, 提升吸引力, match their voice or 文风, improve readability, flow, rhythm, viewpoint, or narrative, while preserving facts, narrative ownership, author perspective, and technical substance.
Capture, incubate, and review verifiable content fragments from daily engineering work — debugging findings, experiments, tool comparisons, pitfalls — for future social posts. Use when the user says to save/log/capture a material or experience fragment, asks what content is ready to write, or wants to review accumulated material fragments by topic or maturity.
| name | idea-next |
| description | Choose one concrete next action from the user's Markdown idea directory. Use when the user invokes $idea-next or asks what to do next, what to work on now, which idea/PR/project to advance, or how to break choice paralysis using previously captured ideas. |
Use the model for judgment: choose the action that best changes the user's situation now, interpret evidence, compare tradeoffs, notice real dependencies, adapt to the user's language, and explain the selected action concretely.
Use scripts/idea_store.py for mechanics: resolve the store, list candidate notes, read likely candidates, and mark a note as doing only when the user asks to start.
python scripts/idea_store.py resolve. If no store exists, ask one short setup question for the idea directory.references/idea-note-schema.md and references/selection-guidance.md.python scripts/idea_store.py list --status open --status doing. Filter by project or user-specified scope when relevant.python scripts/idea_store.py read. If top candidates lack enough context, do at most three small source lookups total, then decide.selection-guidance.md. Do not score mechanically and do not produce a ranking unless asked.python scripts/idea_store.py mark --status doing.Match the user's language and tone in the recommendation. Preserve code names, commands, file paths, API names, and canonical source titles when translating them would reduce clarity.
Answer naturally. Include the chosen action, the concrete evidence-based reason, and the first next step, but do not force fixed headings, labels, order, or formatting. Keep it concise unless the user asks for comparison or detail.