upstream-contributionlisted

Upstream contribution workflow for fork-based development — fork detection, upstream research (issues, PRs, CONTRIBUTING.md, CI patterns), cross-repo issue and PR creation, local tracking issue management, upstream CI monitoring, and guided resolution (merge, rejection, stale). Use when the user says "contribute upstream", "submit to upstream", "fork PR", "upstream PR", "push to upstream", "create upstream issue", "check upstream status", "update tracking", "sync from upstream", "upstream research", or "what's happening upstream". Also activates when the user wants to create a PR targeting a parent/upstream repository from a fork, or needs to check the status of an existing upstream contribution. Requires the current repository to be a GitHub fork. All operations are delegated to the github:github-ops subagent.
f5-sales-demo/marketplace · ★ 0 · Code & Development · score 73

Install: claude install-skill f5-sales-demo/marketplace

**Canonical skill URI**: `skill://github:upstream-contribution` # Upstream Contribution Workflow This skill manages the lifecycle of contributing code from a local GitHub fork to the upstream (parent) repository. It coordinates four phases: Research, Contribute, Track, and Resolve. ALL upstream Git and GitHub operations MUST be delegated to the `github-ops` agent. The main session MUST NOT directly run cross-repo `gh` commands. ## Phases | Phase | When | What happens | | ----- | ---- | ------------ | | Research | User says "contribute upstream" | Fork detection, search upstream issues/PRs, read CONTRIBUTING.md, check CI patterns | | Contribute | Research passes (PROCEED) | Create upstream issue, upstream PR from fork, local tracking issue | | Track | User says "check upstream status" | Poll upstream PR state, update local tracking issue | | Resolve | Upstream PR reaches terminal state | Guided cleanup with user confirmation | ## Phase 1: Research Before contributing anything upstream, the agent must research the upstream repository to avoid duplicates and understand contribution requirements. Delegate with: ```text Agent( subagent_type="github:github-ops", mode="bypassPermissions", prompt="upstream-research: <keywords describing the contribution> Upstream: <owner/repo> Why: <motivation for the contribution>" ) ``` The agent will: 1. Verify this repo is a GitHub fork 2. Search upstream issues (open + closed) for similar work 3. Search upstream PRs (open + cl