菜单
Determine the next available issue number across all change types (feature, fix, workflow) by checking both local docs and remote branches, then reserve it by pushing an empty branch.
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/oocx/tfplan2md --skill next-issue-number命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
基于 SOC 职业分类
正在显示 SKILL.md
| name | next-issue-number |
| description | Determine the next available issue number across all change types (feature, fix, workflow) by checking both local docs and remote branches, then reserve it by pushing an empty branch. |
Ensure unique issue numbering across all change types (feature, fix, workflow) by:
copilot/* remote branches (less than one week old)This prevents duplicate issue numbers when multiple agents work concurrently or when work-in-progress exists on remote branches but not yet in main.
A sessionStart hook (.github/hooks/session-start.json) automatically runs scripts/next-issue-number.sh when a new agent session begins and writes the result to .next-issue-number. This means the next issue number is pre-calculated for you at session start.
Read the pre-calculated value first (fast, no network call required):
if [ -f .next-issue-number ]; then
NEXT_NUMBER=$(cat .next-issue-number)
else
NEXT_NUMBER=$(scripts/next-issue-number.sh)
fi
echo "Next issue number: $NEXT_NUMBER"
The .next-issue-number file is gitignored and refreshed each session. If it is missing or stale, fall back to running the script directly.
scripts/next-issue-number.sh which handles all lookups# Step 1: Determine the next issue number (prefer pre-calculated value from session hook)
if [ -f .next-issue-number ]; then
NEXT_NUMBER=$(cat .next-issue-number)
else
NEXT_NUMBER=$(scripts/next-issue-number.sh)
fi
echo "Next issue number: $NEXT_NUMBER"
# Step 2: Create the branch with the determined number
git fetch origin && git switch main && git pull --ff-only origin main
git switch -c feature/${NEXT_NUMBER}-my-feature-name
# Step 3: IMMEDIATELY push to reserve the number
git push -u origin HEAD
# Now proceed with your work...
if [ -f .next-issue-number ]; then
NEXT_NUMBER=$(cat .next-issue-number)
else
NEXT_NUMBER=$(scripts/next-issue-number.sh)
fi
git fetch origin && git switch main && git pull --ff-only origin main
git switch -c feature/${NEXT_NUMBER}-<short-description>
git push -u origin HEAD
if [ -f .next-issue-number ]; then
NEXT_NUMBER=$(cat .next-issue-number)
else
NEXT_NUMBER=$(scripts/next-issue-number.sh)
fi
git fetch origin && git switch main && git pull --ff-only origin main
git switch -c fix/${NEXT_NUMBER}-<short-description>
git push -u origin HEAD
if [ -f .next-issue-number ]; then
NEXT_NUMBER=$(cat .next-issue-number)
else
NEXT_NUMBER=$(scripts/next-issue-number.sh)
fi
git fetch origin && git switch main && git pull --ff-only origin main
git switch -c workflow/${NEXT_NUMBER}-<short-description>
git push -u origin HEAD
The script will fall back to checking only local docs folders and warn you:
Warning: Could not fetch from GitHub. Using local data only.
Next available number based on local docs: 033
In this case, manually verify on GitHub that no higher numbers exist in remote branches.
The script checks local docs, named branches, and recent copilot/* branches. If it still returns a number that exists:
scripts/next-issue-number.shAfter running the script and pushing your branch:
git ls-remote origin | grep "refs/heads/\(feature\|fix\|workflow\)/${NEXT_NUMBER}-"ls -d docs/{features,issues,workflow}/${NEXT_NUMBER}-* 2>/dev/null (should be empty)