find-issueslisted

Find ripe open-source issues you could actually contribute to — runs across the user's watched-repo list, filters by language/stack/budget, scores each candidate by "is this ripe" signals (no assignee, no linked PR, small scope, recent maintainer activity), and outputs a ranked shortlist with a one-line "why this one". Hands off to /oss-contribute:contribute-upstream once the user picks one.
shiminshen/oss-contribute · ★ 0 · AI & Automation · score 73

Install: claude install-skill shiminshen/oss-contribute

# find-issues The proactive sibling of `contribute-upstream`. Use when the user wants to **shop for** an OSS contribution rather than fix a specific bug they hit. The reactive path is `contribute-upstream` — when in doubt, suggest that one instead, because the user-brought-bug signal beats any ranking heuristic. ## Usage ``` /oss-contribute:find-issues # use profile defaults /oss-contribute:find-issues --lang typescript # filter by language /oss-contribute:find-issues --repo better-auth/better-auth # focus on one repo /oss-contribute:find-issues --budget 30m | 1h | weekend # only suggest issues that fit /oss-contribute:find-issues --refresh # ignore any cached results /oss-contribute:find-issues --trending [daily|weekly] # discover repos via github.com/trending (default: daily) ``` Stable preferences live in the shared profile (see "Profile location" below). Args are per-invocation overrides only. Cap at the flags above — if you need more knobs, edit the profile. ## Profile location Read the profile in this order: 1. `$CLAUDE_PLUGIN_DATA/profile.md` — when running as an installed plugin (Claude Code sets this env var) 2. `~/.claude/plugins/data/oss-contribute/profile.md` — fallback for direct-installed plugins 3. `~/.claude/skills/oss-contribute/profile.md` — fallback for local-development mode If none exist, dispatch to the `profile` skill to set one up before continuing. ## Phase 1 — Load (or