Skip to content

Claude.ai Pulling Open Issues - Some Limitation that Claude is running into #677

Description

@ScooterTech

Report preparation

  • I used the AI-assisted bug report tool (Help → Support → File an Issue)
  • I have attached a support bundle or log file

What happened?

Here's a refined, copy-paste-ready prompt skeleton:


## AetherSDR Issue Helper — Live Data Required

### Step 1 — Paste fresh issue list here:
> Run this first:
> gh issue list --repo ten9876/AetherSDR --state open --limit 200 --json number,title | clip
> (Linux: replace `clip` with `xclip -selection clipboard` or `wl-copy`)

<PASTE ISSUE JSON HERE>

### Step 2 — Paste fresh CLAUDE.md here:
> Run this first:
> curl https://raw.githubusercontent.com/ten9876/AetherSDR/main/CLAUDE.md | clip

<PASTE CLAUDE.md HERE>

### Step 3 — Describe your request:

**Type:** [ ] Feature Request   [ ] Bug Report   [ ] Question

**My idea / issue:**
<DESCRIBE IT HERE>

---
## Instructions for Claude (do not edit below this line)

You are helping contribute to AetherSDR, a Linux-native Qt6/C++20 client 
for FlexRadio transceivers. The project context is in the CLAUDE.md above.

1. DUPLICATE CHECK: Search the pasted issue list for titles and keywords 
   related to the request above. If a duplicate or near-duplicate exists, 
   respond ONLY with:
   > Duplicate found: #<number> — <title>
   > Suggest the user add a +1 and comment there instead.

2. IF NO DUPLICATE: Write a GitHub issue in GitHub-Flavored Markdown with 
   these exact sections:
   - **Title** (concise, imperative, descriptive)
   - **## What** — what the feature does from the user's perspective
   - **## Why** — what problem it solves
   - **## How Other Clients Do It** — how SDR apps (SmartSDR, GQRX, SDR++, 
     SDR#, etc.) implement this, if applicable
   - **## Suggested Behavior** — specific UX: what the user clicks, what 
     they see, what happens. Reference existing AetherSDR UI elements 
     (AppletPanel, VfoWidget, RxApplet, etc.) where relevant.
   - **## Protocol Hints** — relevant FlexLib/SmartSDR TCP commands or 
     VITA-49 stream details if known. If unknown, write:
     `Unknown — needs research`
   - **## Acceptance Criteria** — 3–5 bullet points describing done/not-done

3. Apply labels from this set where appropriate:
   `enhancement` `bug` `audio` `GUI` `spectrum` `protocol` 
   `external devices` `upstream` `SmartLink`

Why each piece is here:

  • The clip/xclip/wl-copy variants cover Windows, X11, and Wayland in one block so users don't have to look it up
  • The Type checkbox reminds the user this works for bugs too, not just features
  • The "do not edit below" line makes it safe to save as a snippet — the instructions stay intact across uses
  • Acceptance Criteria was added because it's missing from the original template and makes issues much more actionable for contributors
  • The AetherSDR UI element callouts (AppletPanel, VfoWidget, etc.) ground the suggested behavior in the actual codebase rather than vague descriptions

Want me to save this as a downloadable .md file?

What did you expect?

Having the AI assistant look and all open issues is a great idea, however I'm sure it can work as the AetherSDR user won't necessarily have a GitHub account and be logged for this to work.

This is slightly above my Clause.ai / GitHub pay grade at this point.

Steps to reproduce

No response

Radio model & firmware

No response

Linux distro & Qt version

No response

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions