release-ls

Check Submariner release status across a 20-step workflow.

3|Updated Sep 30, 2025
One-click install
npx skills add https://github.com/stolostron/submariner-release-management --skill release-ls
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: release-ls
Source: https://github.com/stolostron/submariner-release-management/tree/main/skills/release-ls
Command: npx skills add https://github.com/stolostron/submariner-release-management --skill release-ls

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill provides a clear, step-by-step overview of the Submariner release process, highlighting completed stages, current obstacles, and the immediate next actions required.

Core Features & Use Cases

  • Release Status Monitoring: Get a detailed status of a specific Submariner release version.
  • Blocker Identification: Quickly identify any issues or delays preventing progress.
  • Next Action Guidance: Understand what needs to be done to move the release forward.
  • Use Case: When a release seems stalled, use this Skill to pinpoint exactly where the hold-up is and what the team needs to do next.

Quick Start

Check the status of the '0.22.0' release.

Frequently Asked Questions about release-ls

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

FAQPage Schema
How do I check the status of a stalled Submariner release?

To check a stalled Submariner release status, this Skill retrieves a detailed overview across a 20-step workflow, highlighting completed stages, current blockers, and the immediate next actions required to proceed.

How can I identify what is blocking a Submariner release build?

To identify release blockers, this Skill monitors the Submariner release process and pinpoints exactly where the hold-up is, indicating current obstacles preventing progress and verifying build statuses.

Do I need cluster login to monitor Submariner release progress?

Yes, you need cluster login via `oc login` to monitor Submariner release progress, as the Skill executes a bash script that requires this authentication for detailed status retrieval across the workflow.

What is the best way to debug a failed Submariner release?

The best way to debug a failed Submariner release is using this Skill to execute a status retrieval script, which indicates completed phases and current blockers to help pinpoint the exact failure step.

Can I see which workflow steps are completed during a Submariner release?

Yes, you can see completed workflow steps during a Submariner release, as the Skill checks the status across a 20-step workflow and provides a clear, step-by-step overview of all finished phases.