Fetch and rank open GitHub issues by community engagement, present the top 3 candidates, and plan implementation for the selected issue. Use when the user asks to "pick next issue", "next issue", "which issue should I work on", "top issues", "most popular issues", "prioritize issues", or "what should I work on next".
インストールする前に、エージェントに与えられる指示の中身を確認できます。
Rank open GitHub issues by engagement and plan the selected issue.
Run gh issue list to fetch open issues with engagement data:
gh issue list --state open --json number,title,body,url,reactionGroups,comments,labels,createdAt --limit 50
Calculate an engagement score for each issue:
reactionGroups (thumbs up, heart, hooray, etc.). Weight thumbs-up (THUMBS_UP) reactions 2x since they signal explicit demand.(weighted reactions) + commentsSort issues by engagement score descending.
Present the top 3 issues in a numbered list. For each issue, show:
If fewer than 3 open issues exist, present all of them.
If no open issues exist, inform the user and stop.
Ask the user to pick one of the presented issues (or request to see more).
If the user asks to see more, present the next 3 issues from the ranked list.
Fetch the complete issue details for the selected issue:
gh issue view <number> --json number,title,body,url,labels,comments,reactionGroups,assignees,milestone
Read the full issue body and comments to understand the requirements and any discussion context.
/turboplan SkillRun the /turboplan skill with the issue body as the task description. Tell turboplan that the plan must include a final implementation step: "Close issue #N or reference it in the PR with Closes #N."
gh CLI authenticated with access to the current repogh fails (not in a repo, not authenticated), inform the user and stopまだレビューはありません。使ってみた感想をお寄せください。
概要と使いどころ
Apply findings by making the suggested code changes. Applies accepted verdicts, escalates ambiguous findings to the user, and offers to note genuine improvements for later. Use when the user asks to "apply findings", "apply fixes", "apply suggestions", "apply accepted findings", "fix the findings", or "apply the review results".
日本語の概要は準備中です。原文の説明を表示しています。
Audit the turbo skill lessons that /self-improve writes into this repo's .turbo/handoff/ from other projects, apply the ones the user approves, delete the consumed handoffs, commit and push, and update the installed Turbo skills. Use when the user asks to "read .turbo/handoff and let me know what you think", "read the handoff files and let me know what you think", "review the lesson handoffs", "apply the self-improve handoffs", or "process the turbo handoffs".
日本語の概要は準備中です。原文の説明を表示しています。
Assess project-wide structural technical debt: complexity hotspots, deprecated API usage, duplication clusters, architecture rot, and low-value tests. Ranks findings by impact and refactor effort into a report at .turbo/technical-debt.md. Use when the user asks to "assess technical debt", "find technical debt", "review technical debt", "what should we refactor", "find refactoring candidates", "where is the code rot", "what's our worst code", "find low-value tests", or "which tests can we delete". Analysis-only — does not modify code.
日本語の概要は準備中です。原文の説明を表示しています。
Shared changelog conventions and formatting rules referenced by /create-changelog and /update-changelog. Not typically invoked directly.
日本語の概要は準備中です。原文の説明を表示しています。
Shared changelog conventions and formatting rules referenced by $create-changelog and $update-changelog. Not typically invoked directly.
日本語の概要は準備中です。原文の説明を表示しています。
Run a non-interactive Claude Code print-mode call from Codex. Use when the user asks to "claude print", "ask claude", "run claude", "consult claude", or when a Codex Turbo skill needs Claude as an independent peer reviewer.
日本語の概要は準備中です。原文の説明を表示しています。