PR Babysitter
openinterpreter/openinterpreter
Watches an open GitHub pull request until it merges, handling review comments, diagnosing CI failures and retrying flaky checks along the way.
Fetch and rank open GitHub issues by community engagement, present the top 3 candidates, and plan implementation for the selected issue.
MITAuto-check passed
Install Pick Next Issue
$ npx skills add tobihagemann/turbo --skill pick-next-issue -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install tobihagemann/turbo pick-next-issue --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/tobihagemann/turbo.git skills-src && mkdir -p .claude/skills && cp -r skills-src/codex/skills/pick-next-issue .claude/skills/pick-next-issue && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "pick-next-issue" agent skill from https://github.com/tobihagemann/turbo/tree/main/codex/skills/pick-next-issue into .claude/skills/pick-next-issue/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pick-next-issue", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/tobihagemann/turbo/tree/main/codex/skills/pick-next-issueType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add tobihagemann/turbo --skill pick-next-issue -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install tobihagemann/turbo pick-next-issue --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/tobihagemann/turbo.git skills-src && mkdir -p .agents/skills && cp -r skills-src/codex/skills/pick-next-issue .agents/skills/pick-next-issue && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "pick-next-issue" agent skill from https://github.com/tobihagemann/turbo/tree/main/codex/skills/pick-next-issue into .agents/skills/pick-next-issue/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pick-next-issue", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add tobihagemann/turbo --skill pick-next-issue -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install tobihagemann/turbo pick-next-issue --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/tobihagemann/turbo.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/codex/skills/pick-next-issue .cursor/skills/pick-next-issue && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "pick-next-issue" agent skill from https://github.com/tobihagemann/turbo/tree/main/codex/skills/pick-next-issue into .cursor/skills/pick-next-issue/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pick-next-issue", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/tobihagemann/turbo.git --path codex/skills/pick-next-issue--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add tobihagemann/turbo --skill pick-next-issue -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install tobihagemann/turbo pick-next-issue --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/tobihagemann/turbo.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/codex/skills/pick-next-issue .gemini/skills/pick-next-issue && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "pick-next-issue" agent skill from https://github.com/tobihagemann/turbo/tree/main/codex/skills/pick-next-issue into .gemini/skills/pick-next-issue/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pick-next-issue", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install tobihagemann/turbo pick-next-issueInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add tobihagemann/turbo --skill pick-next-issue -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/tobihagemann/turbo.git skills-src && mkdir -p .github/skills && cp -r skills-src/codex/skills/pick-next-issue .github/skills/pick-next-issue && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "pick-next-issue" agent skill from https://github.com/tobihagemann/turbo/tree/main/codex/skills/pick-next-issue into .github/skills/pick-next-issue/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pick-next-issue", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add tobihagemann/turbo --skill pick-next-issue -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install tobihagemann/turbo pick-next-issue --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/tobihagemann/turbo.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/codex/skills/pick-next-issue .opencode/skills/pick-next-issue && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "pick-next-issue" agent skill from https://github.com/tobihagemann/turbo/tree/main/codex/skills/pick-next-issue into .opencode/skills/pick-next-issue/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pick-next-issue", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
pick-next-issue- GitHub stars
- 408
- Token cost
- ~613 tokens
- SKILL.md length
- 294 words
- Files
- 1
- Skills in repo
- 81
- Repo updated
- First seen
- Licence
- MIT
At a glance
Fetch and rank open GitHub issues by community engagement, present the top 3 candidates, and plan implementation for the selected issue.
- Works in 5 steps: Fetch and Rank Issues → Present Top 3 → User Picks an Issue → …
- The user asks to pick next issue
- SKILL.md covers Step 1: Fetch and Rank Issues, Step 2: Present Top 3, Step 3: User Picks an Issue and Step 4: Read the Full Issue, plus 2 more sections
- Calls gh
What it does
Pick Next Issue is an agent skill from tobihagemann/turbo. 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".
Its SKILL.md is about 610 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It works with GitHub. The repository describes itself as: Reusable workflows for planning, building, reviewing, and shipping with Claude Code and Codex. The licence is MIT.
When your agent uses it
- The user asks to pick next issue
- Which issue should I work on
- Most popular issues
- Prioritize issues
Example prompts
- “pick next issue”
- “next issue”
- “which issue should I work on”
- “/pick-next-issue”
Workflow steps
5 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit 931eda5. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
gh
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use gh, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Pick Next Issue loads about 613 tokens when it runs. Until then it costs about 84 tokens; SKILL.md has 294 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from tobihagemann/turbo at commit 931eda5, republished under its MIT licence (© tobihagemann). 294 words, ~613 tokens.
Download SKILL.mdSave it as
.claude/skills/pick-next-issue/SKILL.md (or your agent's skills folder).- name
- pick-next-issue
- description
- 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".
Pick Next Issue
Rank open GitHub issues by engagement and plan the selected issue.
Step 1: Fetch and Rank Issues
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 50Calculate an engagement score for each issue:
- Reactions score: Sum all reaction counts from
reactionGroups(thumbs up, heart, hooray, etc.). Weight thumbs-up (THUMBS_UP) reactions 2x since they signal explicit demand. - Comments score: Count of comments on the issue.
- Engagement score:
(weighted reactions) + comments
Sort issues by engagement score descending.
Step 2: Present Top 3
Present the top 3 issues in a numbered list. For each issue, show:
- Title with issue number and link
- Labels (if any)
- Engagement: reaction breakdown and comment count
- Created: date
- First paragraph of the issue body (truncate if long)
If fewer than 3 open issues exist, present all of them.
If no open issues exist, inform the user and stop.
Step 3: User Picks an Issue
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.
Step 4: Read the Full Issue
Fetch the complete issue details for the selected issue:
gh issue view <number> --json number,title,body,url,labels,comments,reactionGroups,assignees,milestoneRead the full issue body and comments to understand the requirements and any discussion context.
Step 5: Run $turboplan Skill
Run 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."
Rules
- Requires
ghCLI authenticated with access to the current repo - If
ghfails (not in a repo, not authenticated), inform the user and stop - Never modify issues. This skill is read-only until the implementation is committed.
© tobihagemann, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in codex/skills/pick-next-issue of tobihagemann/turbo.
Open the folder on GitHubat commit 931eda5
Compare with similar skills
Pick Next Issue next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Pick Next Issue this skilltobihagemann/turbo | 408 | — | ~613 | Automated safety check: Pass | MIT | |
| PR Babysitteropeninterpreter/openinterpreter | 69k | 3 repos | ~4.2k | Automated safety check: Pass | Apache-2.0 | |
| Greplooponyx-dot-app/onyx | 32k | 4 repos | ~3.3k | Automated safety check: Pass | MIT | |
| GitHub Deep Researchbytedance/deer-flow | 84k | 4 repos | ~1.3k | Automated safety check: Pass | MIT | |
| Diagnosing Superpowers Sessionsobra/superpowers | 297k | 3 repos | ~1.7k | Automated safety check: Pass | MIT | |
| Update V8 Versionopeninterpreter/openinterpreter | 69k | 2 repos | ~845 | Automated safety check: Pass | Apache-2.0 |
Similar skills
Greploop
onyx-dot-app/onyx
Iteratively improves a PR (GitHub), MR (GitLab), or shelved changelist (Perforce) until Greptile gives it a 5/5 confidence score with zero unresolved comments.
GitHub Deep Research
bytedance/deer-flow
Researches a GitHub repository over four rounds using the GitHub API and web search, then writes a structured markdown report with timeline, metrics and Mermaid diagrams.
Diagnosing Superpowers Sessions
obra/superpowers
Investigates a session where Superpowers went wrong, reads the transcripts on disk and produces an evidence-cited report, optionally prepared as a bug report for the maintainers.
Update V8 Version
openinterpreter/openinterpreter
Bumps the pinned v8 and rusty_v8 versions in Codex, validates the release-candidate path with the v8-canary check, and traces failures to upstream build changes.
Last30days
mvanhorn/last30days-skill
Research what people actually say about any topic in the last 30 days.
More from tobihagemann/turbo
All 81 skills in this repoConsult Oracle
tobihagemann/turbo
Consult ChatGPT Pro via ChatGPT browser automation for problems that resist standard approaches.
Fetch PR Comments
tobihagemann/turbo
Fetch and summarize review feedback and conversation from a GitHub PR (unresolved review threads, review bodies, and PR conversation comments) without making changes.
Recall Rationale
tobihagemann/turbo
Recall why a past change was made by locating the Claude Code transcript that produced it.
Resolve PR Comments
tobihagemann/turbo
Evaluate, fix, answer, and reply to GitHub pull request review comments and conversation comments.
Resolve PR Comments
tobihagemann/turbo
Evaluate, fix, answer, and reply to GitHub pull request review comments and conversation comments.
Assess Technical Debt
tobihagemann/turbo
Assess project-wide structural technical debt: complexity hotspots, deprecated API usage, duplication clusters, architecture rot, and low-value tests.
Related
Works with
Questions about Pick Next Issue
What does Pick Next Issue do?
Fetch and rank open GitHub issues by community engagement, present the top 3 candidates, and plan implementation for the selected issue. Pick Next Issue is an agent skill from tobihagemann/turbo. Fetch and rank open GitHub issues by community engagement, present the top 3 candidates, and plan implementation for the selected issue.
When should I use Pick Next Issue?
Pick Next Issue fits situations like: the user asks to pick next issue; which issue should I work on; most popular issues; prioritize issues.
How do I install Pick Next Issue in Claude Code?
Run `npx skills add tobihagemann/turbo --skill pick-next-issue -a claude-code`. Or copy the skill folder (codex/skills/pick-next-issue in tobihagemann/turbo) into .claude/skills/pick-next-issue in your project. Claude Code loads it when a task matches its description.
How do I install Pick Next Issue in Codex?
Run `npx skills add tobihagemann/turbo --skill pick-next-issue -a codex`. Or copy the skill folder (codex/skills/pick-next-issue in tobihagemann/turbo) into .agents/skills/pick-next-issue in your project. Codex loads it when a task matches its description.
Can I use Pick Next Issue in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add tobihagemann/turbo --skill pick-next-issue -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/pick-next-issue, .gemini/skills/pick-next-issue, .github/skills/pick-next-issue and .opencode/skills/pick-next-issue in your project.
What does Pick Next Issue need to run?
Going by SKILL.md and its folder, Pick Next Issue needs the command-line tools its instructions call (gh).
Does Pick Next Issue access the network?
SKILL.md contains no URLs. Its commands use gh, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is Pick Next Issue safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Pick Next Issue use?
Pick Next Issue is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Pick Next Issue use?
About 613 tokens (SKILL.md is roughly 2.5k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Pick Next Issue?
Skills that share tags, products or a category with Pick Next Issue: PR Babysitter (openinterpreter/openinterpreter, 69k stars), Greploop (onyx-dot-app/onyx, 32k stars), GitHub Deep Research (bytedance/deer-flow, 84k stars) and Diagnosing Superpowers Sessions (obra/superpowers, 297k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Pick Next Issue?
tobihagemann (a GitHub user) maintains it in tobihagemann/turbo, which has 408 GitHub stars. The repository holds 81 skills in this directory. The repository was last updated on October 9, 2026.
Source: tobihagemann/turbo on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.