release-watcher

Detect and analyze upstream codex and opencode releases for downstream impact.

6|Updated Mar 11, 2026

Search Tags:#automation #monitoring #releases #diff-analysis #github-issues #release-watch

Ready to run

npx skills add https://github.com/open-hax/opencode-skills --skill release-watcher

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: release-watcher
Source: https://github.com/open-hax/opencode-skills/tree/main/.opencode/skills/release-watcher
Command: npx skills add https://github.com/open-hax/opencode-skills --skill release-watcher

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Upstream software releases frequently introduce breaking changes or compatibility concerns that can ripple through downstream projects. This skill automates monitoring of codex and opencode releases and surfaces actionable impact to engineering teams.

Core Features & Use Cases

Release polling: Regularly checks for new tags/releases from monitored repositories.
Diff & impact analysis: Detects changes that may affect downstream usage and compatibility.
Issue creation & tracking: Automatically creates GitHub issues labeled codex-release-watch for impacted teams and tracks mitigations.
State management: Maintains last reviewed tag and timestamps to enable incremental monitoring.

Quick Start

Run daily checks to compare the latest codex/opencode releases with the last reviewed tag and open issues for any detected impact.

Frequently Asked Questions about release-watcher

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

FAQPage Schema

How do I monitor upstream software releases for breaking changes?▼

To monitor upstream releases for breaking changes, this Skill polls new tags from target repositories, performs diff analysis to detect downstream impacts, and logs state to enable incremental tracking across daily checks.

How does automated release impact analysis work for downstream projects?▼

Automated release impact analysis works by comparing the latest upstream repository tags against the last reviewed state, identifying modifications that affect compatibility, and generating structured reports for engineering teams.

Can I automatically create GitHub issues when a new release impacts my repository?▼

Yes, you can automatically create GitHub issues. When diff analysis detects a release impact, the workflow opens issues labeled codex-release-watch for impacted teams and tracks mitigations directly within the repository.

Do I need an OpenCode agent workflow to track upstream releases?▼

Yes, you need an OpenCode agent workflow, valid access tokens for repository authentication, and state management configured to log last-reviewed tags and generate incremental impact reports.

What's the best way to detect breaking changes in OpenAI codex and SST opencode releases?▼

The best way to detect breaking changes is running daily checks that diff the latest codex and opencode releases against prior tags, surfacing actionable compatibility concerns and automatically creating labeled tracking issues.

Why does release polling require state management for incremental monitoring?▼

Release polling requires state management to store last reviewed tags and timestamps. This prevents reprocessing identical diffs and ensures the monitoring workflow only analyzes newly introduced upstream changes.