Payload Results YAML

Creates payload-results-{tag}.yaml files for tracking candidate actions and failing jobs.

1|Updated Apr 29, 2026
One-click install
npx skills add https://github.com/openshift-eng/ga-regression-reports --skill payload-results-yaml
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: Payload Results YAML
Source: https://github.com/openshift-eng/ga-regression-reports/tree/main/.claude/skills/payload-results-yaml
Command: npx skills add https://github.com/openshift-eng/ga-regression-reports --skill payload-results-yaml

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill defines the schema for payload-results-{tag}.yaml and provides operations for reading, writing, and mutating the payload results file used by the payload triage pipeline to track candidate actions and failing jobs.

Core Features & Use Cases

  • Defines the metadata, failing_jobs, and candidates structures that capture payload analysis results
  • Supports appending actions (reverts/experiments) and updating statuses in phase 2
  • Enables reading and filtering candidates by confidence and pre-existing revert status
  • Use Case: When analyzing a new payload, create a results file to store failures and candidate actions for rollback or experimentation

Quick Start

Create a new payload-results-{tag}.yaml with the analyze-payload workflow and use it to stage reverts or run experiments.

Frequently Asked Questions about Payload Results YAML

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

FAQPage Schema
How do I store and coordinate payload triage state for failing jobs and revert candidates?▼

You can store and coordinate payload triage state by creating a payload results YAML file. This file establishes a structured schema to track failing jobs, candidate actions, and metadata for downstream analysis.

What is the YAML schema for tracking payload analysis and rollback candidates?▼

The payload results YAML schema defines three core structures: metadata, failing_jobs, and candidates. These fields capture analysis results and enforce safe mutation rules for staging reverts or running experiments.

How do I filter payload revert candidates by confidence level during triage?▼

You can filter payload revert candidates by reading the YAML file and applying confidence thresholds. The schema supports filtering candidates based on confidence levels and pre-existing revert status to streamline triage decisions.

Can I append new revert or experiment actions to an existing payload results YAML file?▼

Yes, you can append new revert or experiment actions to an existing payload results YAML file. The skill supports appending actions and updating statuses during phase 2 of the triage pipeline.

What are the safe mutation rules for updating payload triage YAML files?▼

Safe mutation rules for payload triage YAML files ensure downstream skills can reliably read and update the file. These rules govern how candidates, failing_jobs, and actions are modified without corrupting the triage state.

When do I need a payload results YAML file for pull request automation?▼

You need a payload results YAML file when analyzing a new payload to store failures and candidate actions. It provides a centralized state-management format for coordinating automated rollback or experimentation workflows.