Prowler Pr
Create perfect PRs for Prowler with proper templates and conventions
✨ The solution you've been looking for
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.
See It In Action
Interactive preview & real-world examples
AI Conversation Simulator
See how users interact with this skill
User Prompt
I've made changes to the SDK authentication module. Help me create a proper PR with the template filled out.
Skill Processing
Analyzing request...
Agent Response
A properly formatted PR with filled template sections, conventional commit title, and component-specific checklist items
Quick Start (3 Steps)
Get up and running in minutes
Install
claude-code skill install prowler-pr
claude-code skill install prowler-prConfig
First Trigger
@prowler-pr helpCommands
| Command | Description | Required Args |
|---|---|---|
| @prowler-pr create-a-feature-pr-with-proper-template | Generate a complete pull request following Prowler's conventions including template sections, changelog updates, and component-specific requirements | None |
| @prowler-pr review-pr-requirements-compliance | Validate that your changes meet all Prowler PR requirements before submission | None |
| @prowler-pr multi-component-pr-handling | Handle PRs that span multiple Prowler components (SDK, API, UI, MCP) with appropriate checklists | None |
Typical Use Cases
Create a feature PR with proper template
Generate a complete pull request following Prowler's conventions including template sections, changelog updates, and component-specific requirements
Review PR requirements compliance
Validate that your changes meet all Prowler PR requirements before submission
Multi-component PR handling
Handle PRs that span multiple Prowler components (SDK, API, UI, MCP) with appropriate checklists
Overview
PR Creation Process
- Analyze changes:
git diff main...HEADto understand ALL commits - Determine affected components: SDK, API, UI, MCP, Docs
- Fill template sections based on changes
- Create PR with
gh pr create
PR Template Structure
1### Context
2
3{Why this change? Link issues with `Fix #XXXX`}
4
5### Description
6
7{Summary of changes and dependencies}
8
9### Steps to review
10
11{How to test/verify the changes}
12
13### Checklist
14
15<details>
16
17<summary><b>Community Checklist</b></summary>
18
19- [ ] 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
20- [ ] 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)
21
22</details>
23
24- Are there new checks included in this PR? Yes / No
25 - If so, do we need to update permissions for the provider?
26- [ ] Review if the code is being covered by tests.
27- [ ] Review if code is being documented following https://github.com/google/styleguide/blob/gh-pages/pyguide.md#38-comments-and-docstrings
28- [ ] Review if backport is needed.
29- [ ] Review if is needed to change the Readme.md
30- [ ] Ensure new entries are added to CHANGELOG.md, if applicable.
31
32#### SDK/CLI
33- Are there new checks included in this PR? Yes / No
34 - If so, do we need to update permissions for the provider? Please review this carefully.
35
36#### UI (if applicable)
37- [ ] All issue/task requirements work as expected on the UI
38- [ ] Screenshots/Video - Mobile (X < 640px)
39- [ ] Screenshots/Video - Tablet (640px > X < 1024px)
40- [ ] Screenshots/Video - Desktop (X > 1024px)
41- [ ] Ensure new entries are added to ui/CHANGELOG.md
42
43#### API (if applicable)
44- [ ] All issue/task requirements work as expected on the API
45- [ ] Endpoint response output (if applicable)
46- [ ] EXPLAIN ANALYZE output for new/modified queries or indexes (if applicable)
47- [ ] Performance test results (if applicable)
48- [ ] Any other relevant evidence of the implementation (if applicable)
49- [ ] Verify if API specs need to be regenerated.
50- [ ] Check if version updates are required.
51- [ ] Ensure new entries are added to api/CHANGELOG.md
52
53### License
54
55By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
Component-Specific Rules
| Component | CHANGELOG | Extra Checks |
|---|---|---|
| SDK | prowler/CHANGELOG.md | New checks → permissions update? |
| API | api/CHANGELOG.md | API specs, version bump, endpoint output, EXPLAIN ANALYZE, performance |
| UI | ui/CHANGELOG.md | Screenshots for Mobile/Tablet/Desktop |
| MCP | mcp_server/CHANGELOG.md | N/A |
Commands
1# Check current branch status
2git status
3git log main..HEAD --oneline
4
5# View full diff
6git diff main...HEAD
7
8# Create PR with heredoc for body
9gh pr create --title "feat: description" --body "$(cat <<'EOF'
10### Context
11...
12EOF
13)"
14
15# Create draft PR
16gh pr create --draft --title "feat: description"
Title Conventions
Follow conventional commits:
feat:New featurefix:Bug fixdocs:Documentationchore:Maintenancerefactor:Code restructuretest:Tests
Before Creating PR
- ✅ All tests pass locally
- ✅ Linting passes (
make lintor component-specific) - ✅ CHANGELOG updated (if applicable)
- ✅ Branch is up to date with main
- ✅ Commits are clean and descriptive
Resources
- Documentation: See references/ for links to local developer guide
What Users Are Saying
Real feedback from the community
Environment Matrix
Dependencies
Context Window
Security & Privacy
Information
- Author
- prowler-cloud
- Updated
- 2026-01-30
- Category
- productivity-tools
Related Skills
Prowler Pr
Creates Pull Requests for Prowler following the project template and conventions. Trigger: When …
View Details →Create Pull Request
Create a GitHub pull request following project conventions. Use when the user asks to create a PR, …
View Details →Create Pull Request
Create a GitHub pull request following project conventions. Use when the user asks to create a PR, …
View Details →