prowler-pr

Create and review Prowler pull requests with gh CLI and CI workflow validation.

Updated Jan 19, 2026
One-click install
npx skills add https://github.com/adbertram/Devolutions-CIEM --skill prowler-pr
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: prowler-pr
Source: https://github.com/adbertram/Devolutions-CIEM/tree/main/prowler/skills/prowler-pr
Command: npx skills add https://github.com/adbertram/Devolutions-CIEM --skill prowler-pr

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the creation and review of pull requests for Prowler projects, ensuring PRs follow template conventions and approval workflows.

Core Features & Use Cases

  • Automatic PR creation with gh pr create to enforce project templates.
  • PR requirement reviews: ensures PR template sections, title conventions, and changelog gating.
  • Workflow inspection: reads and validates related CI workflows (.github/workflows/*) like conventional-commit.yml, pr-check-changelog.yml, pr-conflict-checker.yml, labeler.yml, and CODEOWNERS.

Quick Start

Create a PR using the prowler-pr skill that adheres to the repository's PR template and conventional-commit guidelines.

Frequently Asked Questions about prowler-pr

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

FAQPage Schema
How do I automate pull request creation for Prowler projects using GitHub CLI?

Automating pull request creation for Prowler projects uses the gh CLI to run gh pr create, enforcing repository PR templates and conventional-commit guidelines automatically. You need GitHub access and the gh CLI installed to populate templates and initiate PRs.

How do I validate conventional commits and changelog gating in GitHub workflows?

Validating conventional commits and changelog gating involves inspecting CI workflows like conventional-commit.yml and pr-check-changelog.yml in your repository. This process ensures PR titles follow commit conventions and changelog entries are correctly gated before merging.

Does the Prowler PR automation require any specific GitHub repository workflows?

Prowler PR automation requires GitHub access and reads specific CI workflows within .github/workflows, including pr-conflict-checker.yml, labeler.yml, and CODEOWNERS. It validates these files to ensure PR template sections and approval workflows are properly configured.

What's the best way to ensure PR template conformance across Prowler repositories?

The best way to ensure PR template conformance across Prowler repositories is automating PR requirement reviews. This checks that PR template sections, title conventions, and CI workflows like labeler.yml and CODEOWNERS are validated before submission.

Why does my Prowler pull request fail the CI workflow validation?

Prowler pull requests fail CI workflow validation when they do not adhere to template conventions or lack proper changelog gating. The validation process inspects workflows like conventional-commit.yml and pr-check-changelog.yml to enforce strict title and template compliance.

Can I use PR templates to enforce approval workflows with CODEOWNERS?

Yes, you can use PR templates alongside CODEOWNERS to enforce approval workflows. The automation reviews PR requirements by validating the CODEOWNERS file and labeler.yml workflow to ensure correct ownership and labeling during the pull request process.