upstream-integration-governor

Assess and integrate upstream player dependency commits into WebHTV through staged, reversible workflows.

1.3k|385|Updated May 22, 2026
One-click install
npx skills add https://github.com/fish2018/webhtv --skill upstream-integration-governor
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: upstream-integration-governor
Source: https://github.com/fish2018/webhtv/tree/main/webhome-devkit/skills/upstream-integration-governor
Command: npx skills add https://github.com/fish2018/webhtv --skill upstream-integration-governor

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

Merging upstream changes from forks and native player dependencies (FFmpeg, Media3, mpv, IJK) into WebHTV is risky and hard to track. This Skill turns unbounded upstream work into bounded, evidence-backed stages with exhaustive commit ledgers, mandatory best-practice review, and reversible implementation.

Core Features & Use Cases

  • Exhaustive Commit Ledgers: Enumerate every commit across related upstream repositories with full 40-character IDs, explicit dispositions, and cross-repository dependency chains.
  • Gated Implementation: Require a best-practice research review and explicit user approval before any code, lock, patch, or binary change, with atomic commits and annotated recovery tags for rollback.
  • Staged Rollout Planning: Organize work into reversible Exo, MPV, and common stages with defined ordering, acceptance criteria, and validation plans.
  • Use Case: When a new wave of mpv-android or Media3 upstream commits lands, use this Skill to rebuild the merge assessment document, identify the next actionable task, and produce a decision packet before touching any code.

Quick Start

Ask the assistant to assess the latest upstream commits from the WebHTV player dependency repositories and produce the next recommended integration task with its decision packet.

Frequently Asked Questions about upstream-integration-governor

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I assess upstream commits before merging them into a fork?

Build an exhaustive commit ledger enumerating every commit in range with full 40-character IDs, actual diffs, and explicit dispositions such as candidate, superseded, or already implemented. Map cross-repository chains before creating any implementation task.

How to safely integrate mpv or Media3 updates into an Android player app?

Group related commits into reversible Exo, MPV, or common stages, run a mandatory best-practice review comparing no-change, unmodified upstream, and adapted designs, then implement only after explicit approval with atomic commits and recovery tags.

Does this workflow apply to ordinary app bug fixes?

No. The upstream integration workflow is reserved for changes crossing upstream or native contracts such as FFmpeg, Media3, or mpv dependencies. Ordinary app bugs should use a bounded single-patch fix instead.

What happens if an upstream integration needs to be rolled back?

Every approved change is recorded with a rollback anchor, artifact hashes, and an annotated local recovery tag created immediately after the atomic commit. Rollback uses these committed units rather than uncommitted edits.

Why must implementation wait for user approval in this workflow?

The gate prevents unreviewed changes to binary ownership, architecture, or product behavior. A decision-ready plan with evidence, alternatives, risks, and acceptance criteria must be approved before any code, lock, patch, or binary edit.