release-issue-relay

File or comment on deduped GitHub issues for infrastructure failures.

Updated May 1, 2026
One-click install
npx skills add https://github.com/arthur-debert/release --skill release-issue-relay
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: release-issue-relay
Source: https://github.com/arthur-debert/release/tree/main/skills/release-issue-relay
Command: npx skills add https://github.com/arthur-debert/release --skill release-issue-relay

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

release-issue-relay helps you report repeatable infrastructure friction from a consumer repository to the canonical arthur-debert/release repository with enough context for maintainers to fix the root cause.

Core Features & Use Cases

  • Infrastructure-only escalation: Files or comments on GitHub issues only when the consumer can’t fix the underlying problem locally, such as workflow failures, ruleset/policy misbehavior, broken infra templates, or helper-script bugs.
  • Dedupe via matching recent issues: Searches recent open release issues for the same component and symptom and comments on an existing issue instead of creating duplicates, using comment count as a recurrence signal.
  • Incident-context auto-collection: Captures repo identity, current branch, short commit SHA, inferred PR (if any), and the most recent relevant workflow run URL scoped to the current branch.

Quick Start

Run release-issue-relay from the consumer repo after applying a local workaround, providing the COMPONENT and SYMPTOM for the irreparable infrastructure issue, so it can search for a matching open issue and file or comment with full reproduction context.

Frequently Asked Questions about release-issue-relay

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

FAQPage Schema
How do I escalate GitHub workflow failures from a consumer repository to an upstream infra repository?

To escalate GitHub workflow failures, you can run release-issue-relay from the consumer repository to file or comment on a deduped issue in the canonical arthur-debert/release repository. It automatically captures repo identity, branch, commit SHA, and the relevant workflow run URL for context.

How does issue deduplication work when reporting repeatable infrastructure friction?

Issue deduplication works by searching recent open release issues for the same component and symptom before creating a new one. If a matching issue is found, the Skill comments on the existing issue instead of filing a duplicate, using the comment count as a recurrence signal.

Do I need gh CLI authentication and jq to report broken infra templates and policy misbehavior upstream?

Yes, you need gh authenticated access with Issues read/write permissions for arthur-debert/release, plus Bash 4+ and jq. These dependencies are required to parse repository context and successfully file or comment on the upstream GitHub issues.

What incident context is automatically collected when escalating infra helper-script bugs?

When escalating infra helper-script bugs, the Skill automatically collects the repository identity, current branch, short commit SHA, inferred PR if applicable, and the most recent relevant workflow run URL scoped to the current branch with yml/yaml fallback.

When should I not use this approach for workflow failures and ruleset misbehavior?

You should not use this approach when the infrastructure friction can be resolved locally within the consumer repository. It is designed exclusively for irreparable issues like workflow failures, ruleset misbehavior, or broken templates that require upstream maintainers to fix the root cause.