next-issue-number
Installation
SKILL.md
Skill Instructions
Purpose
Ensure unique issue numbering across all change types (feature, fix, workflow) by:
- Finding the highest number used in local docs folders (docs/features/, docs/issues/, docs/workflow/)
- Finding the highest number used in remote branches on GitHub (feature/NNN-, fix/NNN-, workflow/NNN-*)
- Calculating the next available number (max + 1)
- Immediately pushing the new branch to GitHub to reserve the number for other agents
This prevents duplicate issue numbers when multiple agents work concurrently or when work-in-progress exists on remote branches but not yet in main.
Hard Rules
Must
- Check ALL change types (feature, fix, workflow), not just one type
- Check both local docs folders AND remote GitHub branches
- Use the helper script
scripts/next-issue-number.shwhich handles all lookups - Push the new branch immediately after creation (before making any changes) to reserve the number
- Format the number as 3 digits with leading zeros (e.g., 033, 034, 035)
- Minimize Maintainer approvals by using a single stable wrapper script