gh-issuelisted

Analyze and fix the specified GitHub issue: $ARGUMENTS Follow these steps: <!-- recall:begin --> ## Step 0: Prior-art check (RECOMMENDED) Before fixing the issue, recall prior learnings from the global knowledge base so we don't re-learn or re-decide something already captured: ```bash uv run "{{HOME_TOOL_DIR}}/skills/recall/scripts/recall.py" \ "<QUERY>" \ --limit 5 --format markdown ``` **Query construction for `/gh-issue`**: issue title + top labels + repo name (e.g. `"flaky signup test frontend auth"`). **What to do with results:** - If a returned learning names a constraint, anti-pattern, or prior decision directly relevant to the task — surface it to the user BEFORE proceeding with this skill's main flow. - If nothing relevant returns — proceed silently, no need to mention the check. - Never block on recall failure. Empty output / non-zero exit is expected when the KB is absent or the subprocess errors — treat it as "no prior art found", not as an error. <!-- recall:end --> 1. **Get issue details**: - Use `gh issue view $ARGUMENTS` to get the complete issue information - If $ARGUMENTS is not provided, list issues with `gh issue list` and ask which to work on - Understand the problem description, expected behavior, and acceptance criteria 2. **Understand the problem**: - Read through the issue description and any comments carefully - Identify the root cause and scope of the issue - Note any reproduction steps or examples provided 3. **Se