skills.rest
brivaro
brivaroCOMMUNITY
Explore all skills by this author →
GitHub

prowler-ci

Diagnoses and resolves GitHub Actions CI check and pull request gate failures.

Updated Mar 8, 2026
Search Tags:#automation#ci/cd#debugging#pull request#github actions#workflows
One-click install
npx skills add https://github.com/brivaro/brivaro-ai-wizard --skill prowler-ci-brivaro
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: prowler-ci
Source: https://github.com/brivaro/brivaro-ai-wizard/tree/main/skills/prowler-ci
Command: npx skills add https://github.com/brivaro/brivaro-ai-wizard --skill prowler-ci-brivaro

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps diagnose and resolve issues related to GitHub Actions CI checks and gates on Pull Requests, ensuring smooth integration and adherence to project policies.

Core Features & Use Cases

  • CI Check Debugging: Understand why GitHub Actions jobs are failing.
  • Gate Validation: Verify PR title conventions, changelog requirements, and conflict marker checks.
  • Automation Insights: Explain CODEOWNERS/labeler automation and secret scanning.
  • Use Case: A Pull Request is failing its CI checks. Use this Skill to pinpoint the exact workflow, job, and reason for the failure, and suggest a fix.

Quick Start

Use the prowler-ci skill to debug why a GitHub Actions job is failing on my pull request.

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 CI checks on a pull request?▼

Debug failing GitHub Actions CI checks by investigating workflow jobs in `.github/workflows/` to pinpoint exact failure reasons like invalid PR titles, missing changelog entries, or unresolved conflict markers.

Why does my pull request fail CODEOWNERS or labeler automation gates?▼

Pull requests fail CODEOWNERS or labeler automation gates when workflow rules in `.github/workflows/` detect missing approvals, invalid label formats, or unmet policy enforcement requirements configured for the repository.

How do I fix secret scanning failures in GitHub Actions workflows?▼

Fix secret scanning failures in GitHub Actions workflows by identifying the specific job triggering the check, reviewing the flagged content, and removing or securing the detected credentials before pushing updates.

What is the best way to validate PR title conventions and changelog entries in CI?▼

Validate PR title conventions and changelog entries by enforcing automated gate checks within your GitHub Actions workflows, ensuring pull requests meet formatting and documentation requirements before merging.

Can I automate pull request policy enforcement without writing custom GitHub Actions scripts?▼

Automate pull request policy enforcement by configuring standard CI gate validation workflows for title conventions, changelog requirements, and conflict markers rather than maintaining custom automation scripts.

What causes conflict marker checks to fail in GitHub Actions CI?▼

Conflict marker checks fail in GitHub Actions CI when unresolved Git merge conflicts leave raw conflict markers in your files, causing the automated pull request gate validation to block merging.

Related Skills

Explore More Software Engineering Skills→
yanochka11yanochka11

iterate-pr

Iterate pull requests by resolving CI failures and review feedback until validation succeeds.

Community
Advanced
AztecProtocolAztecProtocol
449

fix-pr

Analyze CI logs and apply targeted fixes to failing PRs.

Official
Advanced
Unique-DivineUnique-Divine
6

gh-actionlint

Validate GitHub Actions workflows for syntax and semantic errors.

Community
Intermediate
mlflowmlflow
1

analyze-ci

Analyze failed GitHub Action jobs in pull requests to identify root causes.

Official
Intermediate