Individual skill
pick-next-issue
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".
codex/skills/pick-next-issue/SKILL.md
Source commit d56f17f0ba88ead3a4a77fcdc884f80cd3d10d2f
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- Yes
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Instructions only
- Last checked
- Nov 10, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 420
- Repository last updated
- Nov 9, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- agent-skills Repository topic
- claude-code Repository topic
- claude-skills Repository topic
- developer-tools Repository topic
- skills Repository topic
- codex Repository topic
- codex-skills Repository topic
- agentic-coding Repository topic
- claude-code-plugin Repository topic
- codex-plugin Repository topic
- engineering Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Read excerpt
# 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:
```bash
gh issue list --state open --json number,title,body,url,reactionGroups,comments,labels,createdAt --limit 50
```
Calculate an engagement score for each issue:
