OpenParable
Skip to content
← Back to skills

Prowler PR

Development
prowler-pr

Prowler PR is an Agent Skill for development published in the prowler-cloud/prowler repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.

Creates Pull Requests for Prowler following the project template and conventions. Trigger: When working on pull request requirements or creation (PR template sections, PR title Conventional Commits check, changelog gate/no-changelog label), or when inspecting PR-related GitHub workflows like conventional-commit.yml, pr-check-changelog.yml, pr-conflict-checker.yml, labeler.yml, or CODEOWNERS.

View on GitHub ↗
QUICK START

How to use this skill

Bring this guide into your coding agent with a prompt tailored to the tool you use.

  1. Open your project in Codex.
  2. Copy and paste the prompt below.
  3. Review files and risks before approving any action.
Prompt to paste
Inspect the Agent Skill at https://github.com/prowler-cloud/prowler/blob/HEAD/skills/prowler-pr/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/prowler-pr, but wait for my approval before writing files or running scripts.

Copying this prompt does not install or run the skill. Review third-party files before use.

PR Creation Process

  1. Analyze changes: git diff main...HEAD to understand ALL commits
  2. Determine affected components: SDK, API, UI, MCP, Docs
  3. Fill template sections based on changes
  4. Create PR with gh pr create

PR Template Structure

### Context

{Why this change? Link issues with `Fix #XXXX`}

### Description

{Summary of changes and dependencies}

### Steps to review

{How to test/verify the changes}

### Checklist

<details>

<summary><b>Community Checklist</b></summary>

- [ ] This feature/issue is listed in [here](https://github.com/prowler-cloud/prowler/issues?q=sort%3Aupdated-desc+is%3Aissue+is%3Aopen) or roadmap.prowler.com
- [ ] Is it assigned to me, if not, request it via the issue/feature in [here](https://github.com/prowler-cloud/prowler/issues?q=sort%3Aupdated-desc+is%3Aissue+is%3Aopen) or [Prowler Community Slack](goto.prowler.com/slack)

</details>

- Are there new checks included in this PR? Yes / No
    - If so, do we need to update permissions for the provider?
- [ ] Review if the code is being covered by tests.
- [ ] Review if code is being documented following https://github.com/google/styleguide/blob/gh-pages/pyguide.md#38-comments-and-docstrings
- [ ] Review if backport is needed.
- [ ] Review if is needed to change the Readme.md
- [ ] Ensure a changelog fragment is added under <component>/changelog.d/, if applicable.

#### SDK/CLI
- Are there new checks included in this PR? Yes / No
    - If so, do we need to update permissions for the provider? Please review this carefully.

#### UI (if applicable)
- [ ] All issue/task requirements work as expected on the UI
- [ ] Screenshots/Video - Mobile (X < 640px)
- [ ] Screenshots/Video - Tablet (640px > X < 1024px)
- [ ] Screenshots/Video - Desktop (X > 1024px)
- [ ] Ensure a changelog fragment is added under ui/changelog.d/

#### API (if applicable)
- [ ] All issue/task requirements work as expected on the API
- [ ] Endpoint response output (if applicable)
- [ ] EXPLAIN ANALYZE output for new/modified queries or indexes (if applicable)
- [ ] Performance test results (if applicable)
- [ ] Any other relevant evidence of the implementation (if applicable)
- [ ] Verify if API specs need to be regenerated.
- [ ] Check if version updates are required.
- [ ] Ensure a changelog fragment is added under api/changelog.d/

### License

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Component-Specific Rules

ComponentChangelog fragmentExtra Checks
SDKprowler/changelog.d/New checks → permissions update?
APIapi/changelog.d/API specs, version bump, endpoint output, EXPLAIN ANALYZE, performance
UIui/changelog.d/Screenshots for Mobile/Tablet/Desktop
MCPmcp_server/changelog.d/N/A

Commands

# Check current branch status
git status
git log main..HEAD --oneline

# View full diff
git diff main...HEAD

# Create PR with heredoc for body
gh pr create --title "feat: description" --body "$(cat <<'EOF'
### Context
...
EOF
)"

# Create draft PR
gh pr create --draft --title "feat: description"

Title Conventions

Follow conventional commits:

  • feat: New feature
  • fix: Bug fix
  • docs: Documentation
  • chore: Maintenance
  • refactor: Code restructure
  • test: Tests

Before Creating PR

  1. ✅ All tests pass locally
  2. ✅ Linting passes (make lint or component-specific)
  3. ✅ Changelog fragment added (if applicable)
  4. ✅ Branch is up to date with main
  5. ✅ Commits are clean and descriptive

Before Re-Requesting Review (REQUIRED)

Resolve or respond to every open inline review thread before re-requesting review:

  1. Agreed + fixed: Commit the change. Reply with the commit hash so the reviewer can verify quickly:

    Fixed in abc1234.

  2. Agreed but deferred: Explain why it's out of scope for this PR and where it's tracked.
  3. Disagreed: Reply with clear technical reasoning. Do not leave threads silently open.
  4. Re-request review only after all threads are in a clean state — either resolved or explicitly responded to.

Rule of thumb: A reviewer should never have to wonder "did they see my comment?" when they re-open the PR.

Resources

  • Documentation: See references/ for links to local developer guide