contribute-upstreamlisted

Turn a bug you hit in a third-party dependency (while working in your own project) into an upstream contribution PR — or a well-filed issue if a clean upstream repro isn't feasible. Handles the boring parts — reading CONTRIBUTING, duplicate search, package-manager setup, commit/PR conventions, changesets — and a local patch handoff so the consumer repo isn't blocked.
shiminshen/oss-contribute · ★ 0 · AI & Automation · score 73

Install: claude install-skill shiminshen/oss-contribute

# contribute-upstream Invoke from inside the **consumer** repo (the one that depends on the buggy package), not the upstream itself. You do the boilerplate the user shouldn't have to memorise per-repo; the user provides the bug context. ## Usage ``` /oss-contribute:contribute-upstream <package-name> # e.g. better-auth /oss-contribute:contribute-upstream <package-name> <symptom-summary> /oss-contribute:contribute-upstream # infer package from current stack trace / open file ``` ## Profile location Read the profile in this order (used only for default GitHub account): 1. `$CLAUDE_PLUGIN_DATA/profile.md` 2. `~/.claude/plugins/data/oss-contribute/profile.md` 3. `~/.claude/skills/oss-contribute/profile.md` Profile is **optional** for this skill — the GitHub-account question is asked interactively either way (see Phase 1 step 7). ## Phase 1 — Pre-flight gate (BLOCKING) Do all of the following before touching any code. If any step surfaces a blocker, stop and tell the user; do not proceed unilaterally. 0. **Freshness re-check (FIRST, BLOCKING).** Before *any* other Phase 1 work — before resolving the upstream repo, before dispatching the rules-of-the-road subagent, before reading anything — re-verify the issue is still ripe RIGHT NOW. Even if you just hand-picked it from `find-issues` Phase 4 minutes ago. State changes fast on Hot repos. Single batched call: - `gh issue view <n> --repo <owner>/<repo> --json assignees,closedByPullRequ