Report preparation
What happened?
Exactly right. A hardcoded page=2 breaks the moment you cross 200 issues. Here's the corrected fetch instruction block:
IMPORTANT — before doing anything else, use your web-fetch tool to
download the complete list of open issues. Fetch pages sequentially
starting at page 1, continuing until you receive a page with fewer
than 100 results (which signals the end of the list):
Page 1: https://github.com/ten9876/AetherSDR/issues?state=open&per_page=100&page=1
Page 2: https://github.com/ten9876/AetherSDR/issues?state=open&per_page=100&page=2
Page 3: https://github.com/ten9876/AetherSDR/issues?state=open&per_page=100&page=3
... and so on.
Stop fetching when a page returns fewer than 100 issues — that is the
last page. Do NOT stop early. Do NOT use cached knowledge, training
data, or any previously seen version of these pages.
Collect every issue title and number across all pages before checking
for duplicates. Only after you have the complete list should you proceed.
Also fetch CLAUDE.md fresh before reading it:
https://raw.githubusercontent.com/ten9876/AetherSDR/main/CLAUDE.md
Do not rely on any cached version of this file either.
The termination condition — stop when a page returns fewer than 100 results — is the correct general-purpose approach. It works whether the project has 79 issues today or 799 issues a year from now, with no prompt changes needed.
What did you expect?
No response
Steps to reproduce
No response
Radio model & firmware
No response
Linux distro & Qt version
No response
Report preparation
What happened?
Exactly right. A hardcoded
page=2breaks the moment you cross 200 issues. Here's the corrected fetch instruction block:The termination condition — stop when a page returns fewer than 100 results — is the correct general-purpose approach. It works whether the project has 79 issues today or 799 issues a year from now, with no prompt changes needed.
What did you expect?
No response
Steps to reproduce
No response
Radio model & firmware
No response
Linux distro & Qt version
No response