skills.rest
Globussoft-Technologies
Globussoft-TechnologiesOFFICIAL
Explore all skills by this author →
Website𝕏@globussoftGitHub

medcore-test-triage

Diagnose failing medcore Test workflow runs by clustering assertion failures and classifying root causes.

2|3|Updated Apr 13, 2026
Search Tags:#vitest#github actions#test triage#ci debugging#assertion clustering#cascade root cause#auth contract drift
One-click install
npx skills add https://github.com/Globussoft-Technologies/medcore --skill medcore-test-triage
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: medcore-test-triage
Source: https://github.com/Globussoft-Technologies/medcore/tree/main/.claude/skills/medcore-test-triage
Command: npx skills add https://github.com/Globussoft-Technologies/medcore --skill medcore-test-triage

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you diagnose why a per-push Test workflow in the medcore monorepo suddenly fails with many assertion failures that look unrelated. It speeds up recovery by identifying which underlying root cause is poisoning multiple downstream tests rather than chasing each symptom independently.

Core Features & Use Cases

  • Assertion-level log extraction: Pulls failed assertion text (Expected/Received and relevant error lines) rather than relying only on test names.
  • Failure clustering by symptom: Groups failures into buckets with common status/role/validation patterns to narrow the likely cause.
  • 5-category classification for actionable fixes: Maps clusters into stale-contract, cred mismatch, cascade poisoning, strip-vs-reject layering, or pre-existing.
  • Cascade-root-first fixing strategy: Guides you to prioritize shared mutation/cache/env leakage fixes first to avoid whack-a-mole regressions.
  • CI-to-local verification guardrails: Provides a lightweight local typecheck verification signal appropriate for this repository’s constraints.

Quick Start

Invoke the skill to triage the latest failing per-push Test workflow by cluster diagnosis, starting from the GitHub Actions run logs and ending with a prioritized root-cause fix plan.

Frequently Asked Questions about medcore-test-triage

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

FAQPage Schema
How do I find the root cause of multiple failing vitest tests in a GitHub Actions run?▼

Diagnosing failing vitest test runs involves grouping assertion failures by Expected/Received symptom shape rather than test names. This clustering approach narrows the likely cause across multiple files by highlighting shared status, role, or validation patterns.

Why do my GitHub Actions tests show a sudden green yesterday, red today regression across multiple files?▼

A sudden green yesterday, red today regression across multiple files often indicates cascade poisoning from module-scope mutation or leaked singleFork state. Triage classifies these failures to prioritize shared mutation fixes over chasing individual symptoms.

How do I debug failing CI test workflows after a wave of merges in a monorepo?▼

Debugging failing CI test workflows after a wave of merges requires classifying failure clusters into stale-contract, cred mismatch, cascade poisoning, strip-vs-reject, or pre-existing categories. This produces a prioritized fix order that unblocks downstream failures efficiently.

Can I use assertion clustering to diagnose auth contract drift in CI test failures?▼

Assertion clustering diagnoses auth contract drift by grouping failures with common validation patterns into cred mismatch or stale-contract categories. This distinguishes contract-related changes from cascade poisoning or pre-existing failures.

What's the best way to triage failing tests without chasing each symptom independently?▼

The best way to triage failing tests without chasing symptoms is applying a cascade-root-first fixing strategy. Identifying shared module-scope mutation or leaked state roots unblocks multiple downstream failures rather than fixing them individually.

Does this test triage approach work with vitest workflows that have strip-vs-reject layering issues?▼

This test triage approach works with vitest workflows experiencing strip-vs-reject layering issues by classifying them as a distinct failure category. It applies CI-to-local typecheck verification guardrails to validate fixes within repository constraints.

Related Skills

Explore More Software Engineering Skills→
gioegioe

gh-run

Retrieves GitHub Actions run data and failure logs via gh CLI, generating structured reports with severity-filtered details.

Community
Advanced
baekenoughbaekenough
13

systematic-debugging

Enforce a seven-phase reproduce-first debugging workflow for software failures.

Community
Advanced
edfentonedfenton
3

mern-unit-test

Run MERN monorepo unit tests and generate failure reports.

Community
Advanced
max-sixtymax-sixty
30

ci-fix

Diagnose failing CI builds, apply fixes, and open a pull request.

Community
Advanced