What problem does it solve? Downstream forks often drift into unmaintainable hard forks whose patches rot as upstream moves forward. This Skill keeps every change as an independently buildable, testable, PR-quality patch branch that follows upstream, while a regenerated main or release branch always provides usable integrated code and artifacts. ## Core Features & Use Cases - Structured Branch Model: Separates concerns across patch branches, temporary compatibility branches (tmp/patch/<name>), a ci maintenance branch, and a generated release branch, with a fixed integration order. - Continuous Rebuild & Validation: Rebuilds the release branch from a specific upstream commit, applies upstream PRs and patches in order, runs source and projected-package checks, and pushes safely with --force-with-lease. - Patch Lifecycle Management: Covers adding, maintaining, and retiring patches, including checking upstream issues and PRs before coding and retiring patches once merged upstream. - Use Case: A team maintains a fork of an open-source CLI tool with five unmerged features. The Skill keeps each feature on its own PR-ready branch, rebuilds the release branch nightly via GitHub Actions, and detects conflicts the day upstream changes break a patch. ## Quick Start Ask the agent to maintain this downstream fork against its upstream repository, keep each patch independently reviewable, and rebuild the integrated release branch.
