next-issue-number

The provided skill/instructions are coherent and aligned with the stated purpose: scanning local docs and remote branches to compute and reserve the next issue number by creating/pushing an empty branch. There is no explicit malicious behavior in the instructions themselves. The primary security considerations are (1) the script requires repository write permissions (branch creation) which is a high privilege and must be restricted to trusted agents, (2) a missing helper script (scripts/next-issue-number.sh) prevents full audit — if that script contacted external hosts or forwarded credentials it could be malicious, and (3) operational issues (race conditions, branch clutter) are possible but not malicious. Overall I assess low likelihood of malicious intent in the visible content, but I recommend reviewing the helper script contents before granting execution rights to automated agents.