feat(skills): release lists the open issues the release can close, in Longshot and the launcher #11

Merged
HumanBean merged 1 commit from HumanBean/Tooling:feat/release-issues into main 2026-11-15 23:06:35 +00:00
Owner

After a release, nobody checks which open issues it fixed, so fixed reports stay open, and the ones that look fixed but aren't get closed by mistake. /release now lists both.

What changed

skills/release/SKILL.md has a new step 5, Issues it can close. Steps 1 to 4 are unchanged, and Report moves to step 6. Step 5 looks in both Longshot and LongshotLauncher, whichever one is being released:

  • issues the release's pull requests close by keyword or name;
  • open issues no pull request names but a change fixes, found by reading the body and comments of every open issue whose title touches a changed area;
  • open issues an earlier release already fixed.

An issue counts only when the reporter's problem is the one that was fixed: a comment that narrows a report to a TLS failure rules out an IPv6 fix, and "one of the likely causes" settles nothing until the reporter says it works. The skill never closes or comments on an issue itself. The report ends with Can be closed and Related but staying open.

How it was tested

The new step was done by hand on LongshotLauncher v1.0.0-rc.8. It found nothing to close: #100 was already closed by #111. It found four related issues that stay open: Longshot#738 (the reporter's failure is at TLS, not IPv6), Longshot#917, Longshot#744 and Longshot#411 (that one is waiting on Longshot#685).

python -I -B tests/run_all.py: 3 of 4 pass. The failure is test_forge_pr.py's test_create_draft_is_the_default_and_wip_is_not_doubled, which tests forge.py pr create. This pull request changes only the skill's Markdown.

🤖 Generated with Claude Code

After a release, nobody checks which open issues it fixed, so fixed reports stay open, and the ones that look fixed but aren't get closed by mistake. `/release` now lists both. ## What changed `skills/release/SKILL.md` has a new step 5, *Issues it can close*. Steps 1 to 4 are unchanged, and *Report* moves to step 6. Step 5 looks in both Longshot and LongshotLauncher, whichever one is being released: - issues the release's pull requests close by keyword or name; - open issues no pull request names but a change fixes, found by reading the body and comments of every open issue whose title touches a changed area; - open issues an earlier release already fixed. An issue counts only when the reporter's problem is the one that was fixed: a comment that narrows a report to a TLS failure rules out an IPv6 fix, and "one of the likely causes" settles nothing until the reporter says it works. The skill never closes or comments on an issue itself. The report ends with **Can be closed** and **Related but staying open**. ## How it was tested The new step was done by hand on LongshotLauncher v1.0.0-rc.8. It found nothing to close: #100 was already closed by #111. It found four related issues that stay open: Longshot#738 (the reporter's failure is at TLS, not IPv6), Longshot#917, Longshot#744 and Longshot#411 (that one is waiting on Longshot#685). `python -I -B tests/run_all.py`: 3 of 4 pass. The failure is `test_forge_pr.py`'s `test_create_draft_is_the_default_and_wip_is_not_doubled`, which tests `forge.py pr create`. This pull request changes only the skill's Markdown. 🤖 Generated with [Claude Code](https://claude.com/claude-code)
HumanBean deleted branch feat/release-issues 2026-11-15 23:06:35 +00:00
Sign in to join this conversation.
No reviewers
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
MagicBeanDev/Tooling!11
No description provided.