seed-snapshot-release

Triggers and monitors GitHub Actions snapshot releases for pull requests via gh CLI.

1.1k|89|Updated Mar 11, 2021
One-click install
npx skills add https://github.com/daangn/seed-design --skill seed-snapshot-release
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: seed-snapshot-release
Source: https://github.com/daangn/seed-design/tree/main/skills/seed-snapshot-release
Command: npx skills add https://github.com/daangn/seed-design --skill seed-snapshot-release

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manually posting /snapshot comments, tracking the Continuous Releases workflow, and digging out tarball URLs from PR comments is repetitive and error-prone. This Skill automates the entire snapshot-release loop for the PR tied to your current branch.

Core Features & Use Cases

  • Trigger or resume: Posts a /snapshot comment when none exists, or picks up an in-flight/finished run without duplicating work (re-entrant design).
  • Safety checks before triggering: Detects uncommitted changes and unpushed commits, warns that snapshots build from remote HEAD, and can push first with your confirmation.
  • Wait and report: Watches the matching Continuous Releases workflow run, then surfaces the 📦 Snapshot Release comment with tarball URLs, plus failed steps on errors.
  • Use Case: You just pushed a fix to a SEED Design PR and want a preview build. Invoke the skill, confirm the trigger, and get back installable pkg.pr.new tarball URLs once CI finishes.

Quick Start

Ask the assistant to trigger a snapshot release for the current branch's PR and notify you with the tarball URLs when it finishes.

Frequently Asked Questions about seed-snapshot-release

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

FAQPage Schema
How do I trigger a snapshot release for a GitHub pull request?

Post a comment containing exactly /snapshot on the PR, which triggers the Continuous Releases GitHub Actions workflow. This skill automates that step, waits for the run to finish, and reports the resulting tarball URLs from the 📦 Snapshot Release comment.

How do I wait for a GitHub Actions workflow run to finish from the CLI?

Use gh run watch <run-id> --exit-status to stream a run until completion and preserve its exit code. The skill locates the matching run via gh run list filtered by workflow file, issue_comment event, and creation time, then watches it in the background.

Why is my snapshot build missing my latest local changes?

Snapshot releases are built by GitHub Actions from the PR's remote HEAD, so uncommitted changes and unpushed commits are silently excluded. Commit and push before posting /snapshot; the skill detects this state and offers to push first.

Why doesn't filtering workflow runs by branch find the snapshot run?

The Continuous Releases workflow runs on the issue_comment event in the default branch context, so its headBranch never matches the PR branch. Match runs by workflow filename, event type, and creation timestamp instead of --branch.

What happens if the snapshot skill is interrupted mid-run?

The skill is re-entrant: re-invoking it finds the existing /snapshot comment, picks up the in-flight workflow run via gh run watch, and reports the result. No cleanup or manual state recovery is needed.