prowler-pr

Automates Prowler pull request creation and governance with templates and CI checks.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill automates the creation and governance of Prowler pull requests, ensuring consistency with project templates and conventions.

Core Features & Use Cases

  • Automatically generate PRs that adhere to the repository's PR template
  • Validate PR titles, commit messages, and changelog gates
  • Inspect related workflows to verify PR CI checks and CODEOWNERS ownership

Quick Start

Create a PR using gh pr create and verify templates, titles, and changelog gating.

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 to enforce PR templates and conventional commits?

Automating pull request creation enforces PR templates, conventional commits, and changelog gates by validating titles and commit messages against repository conventions before submission.

What is the best way to validate CODEOWNERS checks and CI workflows for a GitHub pull request?

Validating CODEOWNERS checks and CI workflows requires inspecting related GitHub workflows to verify ownership rules and continuous integration checks are satisfied during pull request handling.

Can I use GitHub CLI to generate pull requests that automatically pass changelog gating?

Using GitHub CLI to create pull requests can pass changelog gating when automation validates commit messages, PR titles, and templates against required repository conventions before submission.

Does automating PR governance help maintain consistency across Prowler repository conventions?

Automating PR governance maintains consistency across Prowler repository conventions by applying standardized templates, enforcing conventional commits, and verifying CI checks during pull request creation.

Why does my pull request fail CI checks when missing the required PR template?

Pull requests fail CI checks when missing required PR templates because governance automation validates template adherence, commit message conventions, and changelog gates before allowing submission.

What pull request conventions do I need to follow to pass automated Prowler PR checks?

To pass automated Prowler PR checks, pull requests must satisfy PR template requirements, conventional commit formatting, changelog gates, and CODEOWNERS ownership validations enforced by the workflow.