prowler-ci

Automate Prowler CI checks and PR gates for GitHub Actions workflows.

Updated Feb 18, 2026
One-click install
npx skills add https://github.com/vanhoangkha/cloud-security-audit --skill prowler-ci-vanhoangkha
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: prowler-ci
Source: https://github.com/vanhoangkha/cloud-security-audit/tree/main/multi-cloud/prowler/skills/prowler-ci
Command: npx skills add https://github.com/vanhoangkha/cloud-security-audit --skill prowler-ci-vanhoangkha

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill streamlines the Continuous Integration and Continuous Deployment (CI/CD) process for the Prowler project by automating checks and gates on Pull Requests (PRs), ensuring code quality and adherence to project standards before merging.

Core Features & Use Cases

  • PR Checks: Validates PR titles against Conventional Commits, checks for necessary changelog updates, and verifies the absence of merge conflict markers.
  • Secret Scanning: Integrates TruffleHog to detect and prevent accidental leakage of sensitive information within the codebase.
  • Automation: Manages CODEOWNERS and labeler automation for efficient PR triaging and review assignment.
  • Use Case: When a developer opens a Pull Request, this Skill automatically runs checks to ensure the PR title follows the expected format, a changelog entry is included if necessary, and no secrets are exposed, preventing common CI failures and security risks.

Quick Start

Use the prowler-ci skill to debug why a GitHub Actions job is failing on a 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 validate pull request titles and changelog updates in GitHub Actions CI?

To validate pull request titles and changelog updates in GitHub Actions CI, you can enforce Conventional Commits formats and changelog gates. This automatically verifies PR titles follow expected formats and required entries are included before merging.

Why does my CI check fail when opening a pull request without a changelog entry?

Your CI check fails because changelog enforcement gates require an update entry unless a no-changelog label is applied. This validation prevents merging code changes without documenting the updates in the repository's changelog.

What is the best way to scan for secrets and merge conflict markers in a pull request?

The best way to scan for secrets and merge conflict markers in a pull request is integrating TruffleHog for secret detection alongside automated conflict marker checks. This prevents sensitive information leakage and broken code from merging.

Can I use CODEOWNERS and labeler automation for PR triaging within .github/workflows?

Yes, you can use CODEOWNERS and labeler automation within .github/workflows to manage PR triaging and review assignment. This automatically assigns reviewers and applies labels based on modified paths to streamline the process.

How do I debug failing GitHub Actions jobs on a Prowler repository pull request?

To debug failing GitHub Actions jobs on a Prowler repository pull request, analyze the workflow validation outputs for PR title, changelog, or secret scanning failures. This identifies which specific CI gate blocked the merge.