skills.rest
oobagi
oobagiCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

release

Discover and trigger the configured release mechanism for a target.

Updated Aug 23, 2026
Search Tags:#automation#workflow#versioning#monitoring#release#ci-cd
One-click install
npx skills add https://github.com/oobagi/jflow --skill release-oobagi
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: release
Source: https://github.com/oobagi/jflow/tree/main/skills/release
Command: npx skills add https://github.com/oobagi/jflow --skill release-oobagi

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Cut release processes across repositories short by automating discovery of the release mechanism, triggering the release, and monitoring progress to completion.

Core Features & Use Cases

  • Discover and trigger the configured release mechanism (GitHub Actions workflow, npm publish, cargo publish, Python publish, Docker push, or a custom script) and control the target (preview or production).
  • Preflight checks, version stashing, and guardrails to prevent accidental production releases.
  • Monitor release progress until completion and report status with links to workflows or artifacts.
  • Optional mobile screenshot capture via Maestro MCP for mobile projects, to document new features during release.

Quick Start

Run the release skill with a target (preview or production) and optional --screenshots flag to publish a new artifact and monitor the workflow to completion.

Frequently Asked Questions about release

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

FAQPage Schema
How do I automate project releases across different repositories?▼

Automate project releases by discovering the configured release mechanism, such as GitHub Actions or npm publish, triggering it with a target, and monitoring progress until completion to cut manual release processes short.

Can I trigger npm publish or cargo publish automatically from my repository?▼

Yes, the release process automatically discovers and triggers configured mechanisms including npm publish, cargo publish, Python publish, Docker push, or custom scripts based on your repository setup.

How do I prevent accidental production releases during CI/CD automation?▼

Prevent accidental production releases by enforcing strict preflight validation, uncommitted changes checks, and mandatory user confirmation specifically for production targets before triggering the workflow.

Does GitHub Actions release monitoring support mobile screenshot capture?▼

Yes, mobile projects can optionally capture screenshots via Maestro MCP during the release process to visually document new features while monitoring workflow progress.

What preflight checks are needed before triggering a version release?▼

Preflight checks for version releases include validating the environment, checking for uncommitted changes, and stashing versions to ensure a clean state before triggering and monitoring the release.

Related Skills

Explore More Software Engineering Skills→
elbrunoelbruno
2

ci-validation-gates

Enforce CI/CD gates validating semver, NPM_TOKEN, and release events.

Community
Advanced
getsentrygetsentry
20

sentry-fix-issues

Identify and fix Sentry production issues with validated code changes.

Official
Advanced
nicolehaugennicolehaugen

ci-validation-gates

Validate CI/CD pipelines for semver, token types, retry logic, and draft detection.

Community
Advanced
fusenginefusengine
22

dependency-audit

Audit project dependencies for known security vulnerabilities using ecosystem-specific tools.

Community
Intermediate