prow-autofix

Analyze Prow job failures and create pull requests with generated fixes.

12|Updated Mar 6, 2026
One-click install
npx skills add https://github.com/openshift-online/rosa-gap-analysis --skill prow-autofix
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: prow-autofix
Source: https://github.com/openshift-online/rosa-gap-analysis/tree/main/skills/prow-autofix
Command: npx skills add https://github.com/openshift-online/rosa-gap-analysis --skill prow-autofix

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires oc, jq, gcloud, python3, PyYAML, yq, gh, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill streamlines the process of identifying, analyzing, and addressing Prow job failures by automatically generating necessary files, validating them, and creating pull requests, making the workflow efficient and less error-prone.

Core Features & Use Cases

  • Automated Failure Analysis: Analyzes the most recent failed CI job, extracting necessary details without manual intervention.
  • PR Creation: Generates files for AWS STS policies, GCP WIF templates, and acknowledgment files, then creates a pull request for them.
  • Validation and Cleanup: Validates all generated files and ensures that the temporary directories are cleaned up after the process.
  • Use Case: In a CI/CD pipeline, after a job fails, automatically analyze the failure, create a pull request with the necessary fixes, and clean up the temporary files.

Quick Start

Run the 'prow-autofix' command to start the automated fix process for the latest failed job.

Frequently Asked Questions about prow-autofix

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

FAQPage Schema
How do I automate pull request creation for Prow job failures?

To automate pull request creation for Prow job failures, this Skill analyzes the failed CI job, generates files like AWS STS policies and GCP WIF templates, and automatically opens a pull request with the required fixes.

What is the best way to generate AWS STS policies and GCP WIF templates after a CI failure?

The best way to generate AWS STS policies and GCP WIF templates after a CI failure is using an automated remediation workflow that extracts failure details, validates the configuration files, and cleans up temporary directories post-creation.

Do I need gh and yq installed to automate Prow failure analysis?

Yes, you need gh and yq installed, along with oc, jq, gcloud, python3, and PyYAML, to operate this automated Prow failure analysis and PR creation workflow effectively within your CI/CD pipeline.

Can I use prow-autofix to automatically validate generated acknowledgment files?

Yes, you can use prow-autofix to automatically generate and validate acknowledgment files, ensuring the configurations for AWS STS and GCP WIF are correct before creating the pull request.

How does automated remediation handle temporary directories after PR creation?

Automated remediation handles temporary directories by validating all generated files first, then ensuring the temporary directories are thoroughly cleaned up after the pull request creation process completes.