medcore-release

Dispatch MedCore's GitHub Actions release validation workflow and wait for completion.

2|3|Updated Apr 13, 2026
One-click install
npx skills add https://github.com/Globussoft-Technologies/medcore --skill medcore-release
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: medcore-release
Source: https://github.com/Globussoft-Technologies/medcore/tree/main/.claude/skills/medcore-release
Command: npx skills add https://github.com/Globussoft-Technologies/medcore --skill medcore-release

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents wasted time and unclear debugging by automatically running MedCore’s release.yml validation workflow and returning a focused failure diagnosis.

Core Features & Use Cases

  • Release workflow dispatch & completion: Kicks off the “Release validation” GitHub Actions workflow on the current target SHA and waits for it to finish.
  • Failure-first log triage: On failure, surfaces the first ~100 log lines and isolates likely failing tests for immediate next steps.
  • Safety against duplicates: Detects in-flight runs on the same SHA to avoid dispatching redundant 25–40 minute CI jobs.
  • Use case: After landing a change affecting routes, schemas, or middleware, run the full Playwright + integration + WebKit suite and get an actionable failure report rather than manually hunting through CI logs.

Quick Start

Ask to run release.yml validation on the current origin/main commit and report exactly which tests failed along with the first relevant log lines.

Frequently Asked Questions about medcore-release

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

FAQPage Schema
How do I automatically trigger a GitHub Actions release validation workflow on a specific commit?

To trigger release validation, this Skill dispatches the GitHub Actions release.yml workflow on the current target commit SHA and waits for completion. It automatically prevents duplicate in-flight runs for the same SHA to avoid redundant CI jobs.

How do I get focused failure logs from a Playwright WebKit end-to-end test run?

Getting focused failure logs from a Playwright WebKit test run is handled by applying log-failed filtering to isolate likely failing tests. It surfaces the first 100 relevant log lines to provide concise, test-focused diagnostics for immediate debugging next steps.

How can I prevent duplicate GitHub Actions runs on the same commit SHA?

Preventing duplicate GitHub Actions runs on the same commit SHA is achieved by detecting in-flight CI jobs before dispatching. This safety check avoids queuing redundant 25 to 40 minute release validation workflows for an already running commit.

When should I run full integration and Playwright release validation checks?

Full integration and Playwright release validation checks should be run after landing meaningful code changes affecting routes, schemas, or middleware. This verifies the end-to-end suite, including WebKit, and returns an actionable failure report.

Does this release validation workflow require any specific dependencies or components to run?

Release validation requires no external dependencies or components to run. It uses standard GitHub CLI commands like gh run listing and exit-status watching to dispatch the workflow, monitor completion, and extract failure logs natively.