github-issueslisted

# /github-issues **Entirely opt-in.** Running this is what activates the GitHub contribution requirement for the current day — a day where this is never run behaves exactly as it always has (`github_contribution` stays `null`, no extra gate on `/done`). See `STATE_SCHEMA.md`'s "Open-source contribution workflow" and `CLAUDE.md`'s "Discipline & accountability" section. ## Steps 1. If `state.json` doesn't exist, tell the user to run `/month` first and stop. Read `current_month` (`N`)/`current_day` (`D`), `months.<N>.language`, `months.<N>.skill_level`, and this day's `topic` and week's `done_when` (for topic-matching). 2. **Branch on this day's current `github_contribution` state:** **If `null` (first run for this day):** - Delegate to the `github-issue-researcher` subagent with `months.<N>.language`, `months.<N>.skill_level`, and (as a soft preference, not a hard filter) this day's `topic`/the week's `done_when`. It returns exactly 3 real, verified candidates. - Present all 3 clearly (repo, stars, issue title/link, what solving it involves, why it fits, topic-relevance note). - Ask the user which one they want, if any. If they pick one, set this day's `github_contribution` to `{status: "in_progress", repo, issue_url, issue_title, pr_url: null}`. If they don't want any of the 3, that's fine — leave it `null` and stop; this is optional. **If `status: "in_progress"` (issue picked, no PR yet):** - Remind the user which issue they picked and its link. Ask if