What problem does it solve? A fix or feature implemented in a consumer repository often really belongs in one of its dependencies. This Skill handles the two-repository case: it clones the upstream project, reimplements the change under that project's conventions, verifies the consumer against a local build, opens the upstream PR, and re-points the consumer at the published release — while preventing private-project details from leaking into public upstream artifacts. ## Core Features & Use Cases - Ecosystem-neutral upstream resolution: Discovers the upstream repository from package manifests across npm, PyPI, crates.io, Go modules, and RubyGems, then detects each project's own build, test, and lint commands. - Consumer confidentiality enforcement: Blocks consumer names, URLs, brand values, and internal identifiers from appearing in any upstream commit, PR, comment, or fixture when the upstream is public and the consumer is private. - Local-build verification and rewiring: Links the consumer to the local upstream build (npm link, pip -e, Cargo patch, Go replace, Gem path), confirms it works, removes the local implementation, and unlinks before committing. - Use Case: Your app carries a patched Badge component that belongs in the public design-system library. The skill clones the library, implements the change following its CONTRIBUTING.md, opens the upstream PR, and after merge and release bumps your dependency to the published version. ## Quick Start Ask the agent to upstream the local Badge component changes into the design-system dependency and rewire this repo onto the released version.
