prowler-ci

Diagnose GitHub Actions PR CI failures and gate behaviors in Prowler repositories.

14.6k|2.3k|Updated Aug 24, 2016
One-click install
npx skills add https://github.com/prowler-cloud/prowler --skill prowler-ci-prowler-cloud
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: prowler-ci
Source: https://github.com/prowler-cloud/prowler/tree/main/skills/prowler-ci
Command: npx skills add https://github.com/prowler-cloud/prowler --skill prowler-ci-prowler-cloud

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates understanding and debugging of CI gates and PR checks in a Prowler repository, reducing time to identify failures and non-compliant workflows.

Core Features & Use Cases

  • Diagnose failing GitHub Actions workflows under .github/workflows and explain why checks fail.
  • Clarify PR title validations, changelog gate behavior, and CODEOWNERS/labeler automation.
  • Guidance for adjusting workflows, gates, and labels to align with PR requirements.

Quick Start

Inspect a failing PR CI check and request a concise explanation of the implicated workflow and gate.

Frequently Asked Questions about prowler-ci

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

FAQPage Schema
How do I debug failing GitHub Actions workflows in a Prowler repository?

To debug failing GitHub Actions workflows, you inspect the workflow definitions under .github/workflows alongside PR metadata to identify the failing CI gate and guide remediation based on the configuration.

Why does my PR title validation check fail in Prowler CI?

PR title validation fails when the PR metadata does not match the expected CI gate configuration. Diagnosing the behavior involves reading the workflow definitions to clarify the enforced title rules.

How do I fix changelog gate failures for GitHub PR checks?

Fixing changelog gate failures requires reading the CI gate configurations to understand the missing changelog requirements, then adjusting the PR to align with the enforced repository gates.

Can I use this to troubleshoot CODEOWNERS and labeler automation in GitHub Actions?

Yes, you can troubleshoot CODEOWNERS and labeler automation by reading the workflow definitions and PR metadata to clarify the automation behavior and guide adjustments to the label requirements.

What is the best way to resolve conflict marker checks in a Prowler PR gate?

The best way to resolve conflict marker checks is to diagnose the PR gate behaviors by reading the CI configuration, which explains why the check fails and guides remediation of the merge conflicts.

Does prowler-ci work without external dependencies to diagnose PR gate behaviors?

Yes, diagnosing PR gate behaviors works without external dependencies by directly reading GitHub Actions workflows, PR metadata, and common CI gate configurations to explain failures and guide remediation.