qualify-oliphaunt-change

Select and execute qualification gates for Oliphaunt changes.

94|10|Updated Sep 27, 2025
One-click install
npx skills add https://github.com/f0rr0/oliphaunt --skill qualify-oliphaunt-change
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: qualify-oliphaunt-change
Source: https://github.com/f0rr0/oliphaunt/tree/main/.codex/skills/qualify-oliphaunt-change
Command: npx skills add https://github.com/f0rr0/oliphaunt --skill qualify-oliphaunt-change

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents incomplete or misleading qualification of Oliphaunt changes by selecting the right local checks, validating exact commit evidence, and diagnosing failures before merge or release.

Core Features & Use Cases

  • Change-Aware Qualification: Uses repository task ownership and affected-project analysis to choose focused checks without relying on directory names alone.
  • Release and Policy Validation: Runs the required release, asset, extension, workflow, SDK, source-acquisition, and platform-specific gates when their contracts change.
  • Exact-SHA CI Evidence: Verifies GitHub workflow runs, required gates, artifacts, publication locks, platform compatibility evidence, and WASIX lifecycle results for the precise candidate commit.
  • Failure Diagnosis: Identifies the earliest causal error, distinguishes skipped lanes from failed checks, and requires restarting qualification for a corrected commit.
  • Use Case: Before releasing an SDK, workflow, extension, or WASIX runtime change, use this Skill to select the affected Moon tasks, run the appropriate local gates, and confirm that the exact GitHub commit is publishable.

Quick Start

Use the qualify-oliphaunt-change skill to qualify the current Oliphaunt change before merge or release and report commands, outcomes, skipped lanes, exact-SHA CI evidence, and residual platform gaps.

Frequently Asked Questions about qualify-oliphaunt-change

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

FAQPage Schema
How do I validate exact commit evidence for GitHub CI workflow runs before a release?

Release readiness validation runs required release, asset, extension, workflow, SDK, and platform-specific gates when their contracts change. It confirms the exact GitHub commit passes all required checks before publication.

How do I select the correct local checks for an SDK testing or workflow policy change?

Change-aware qualification uses repository task ownership and affected-project analysis to choose focused Moon tasks. It selects appropriate local gates without relying on directory names alone for SDK or workflow policy changes.

Why does GitHub CI show skipped lanes during release validation, and how do I diagnose the failure?

Failure diagnosis identifies the earliest causal error and distinguishes skipped lanes from failed checks. You must restart qualification using a corrected commit to resolve the detected validation failures.

Does release validation support WASIX lifecycle evidence and platform compatibility review?

Yes, qualification verifies WASIX lifecycle results and platform compatibility evidence for the exact candidate commit. It runs platform-specific gates when runtime or platform contracts change.