prowler-compliance-review — Claude Code skill: setup and features
prowler-compliance-review reviews pull requests adding or updating compliance frameworks in Prowler. Validates JSON schemas, detects duplicate IDs, and flags missing checks.
Apache-2.0 ★ 15,302 updated 2026-10-25
npx skills add prowler-cloud/prowler --skill prowler-compliance-review -a claude-codeWhat prowler-compliance-review does
This skill guides the review of compliance frameworks such as CIS, NIST, or PCI-DSS inside the Prowler repository. It inspects JSON declarations inside prowler/compliance/{provider}/, validating syntax with python3 -m json.tool and running the bundled validate_compliance.py script. The review tree confirms that all referenced checks exist in the codebase and that requirement IDs remain unique.
It also verifies supporting artifacts across the repository. If an automated requirement lacks check definitions, or if the PR diff misses a fragment file under prowler/changelog.d/, the skill halts the review and requests changes.
What it helps with
- Validate compliance JSON schema syntax before merging a PR
- Catch missing check implementations and duplicate requirement IDs
- Verify that changelog fragments exist under prowler/changelog.d
- Check dashboard template consistency in dashboard/compliance
Example prompts for the agent
- Review this pull request updating the CIS AWS compliance framework
- Run the validation script on prowler/compliance/aws/cis_3.0.json
- Check whether all rules in the new NIST framework exist in the codebase
How to install prowler-compliance-review
1Skills CLI (Vercel)
npx skills add prowler-cloud/prowler --skill prowler-compliance-review -a claude-code2Manually: put the files in place
~/.claude/skills/prowler-compliance-review/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/prowler-compliance-review/
1Skills CLI (Vercel)
npx skills add prowler-cloud/prowler --skill prowler-compliance-review -a codex2Manually: put the files in place
.agents/skills/prowler-compliance-review/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add prowler-cloud/prowler --skill prowler-compliance-review -a cursor2Manually: put the files in place
.cursor/skills/prowler-compliance-review/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install prowler-cloud/prowler skills/prowler-compliance-review2Manually: put the files in place
.github/skills/prowler-compliance-review/SKILL.md1Skills CLI (Vercel)
npx skills add prowler-cloud/prowler --skill prowler-compliance-review -a gemini-cli2Platform CLI
gemini skills install https://github.com/prowler-cloud/prowler --path skills/prowler-compliance-reviewManually: put the files in place
.devin/skills/prowler-compliance-review/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add prowler-cloud/prowler --skill prowler-compliance-review -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about prowler-compliance-review
How to install prowler-compliance-review in Claude Code?
Run npx skills add prowler-cloud/prowler --skill prowler-compliance-review -a claude-code. The definition is saved to ~/.claude/skills/prowler-compliance-review/SKILL.md.
What does prowler-compliance-review do?
It applies a structured review checklist to pull requests touching compliance frameworks, ensuring JSON validity, metadata completeness, and dashboard compatibility.
Which issues cause the review decision tree to fail?
The check fails immediately on broken JSON syntax, duplicate requirement IDs, or references to checks that do not exist in the repository.
Source text
SKILL.md · Apache-2.0
---
name: prowler-compliance-review
description: >
Reviews Pull Requests that add or modify compliance frameworks.
Trigger: When reviewing PRs with compliance framework changes, CIS/NIST/PCI-DSS additions, or compliance JSON files.
license: Apache-2.0
metadata:
author: prowler-cloud
version: "1.0"
scope: [root, sdk]
auto_invoke: "Reviewing compliance framework PRs"
allowed-tools: Read, Edit, Write, Glob, Grep, Bash, WebFetch, WebSearch, Task
---
## When to Use
- Reviewing PRs that add new compliance frameworks
- Reviewing PRs that modify existing compliance frameworks
- Validating compliance framework JSON structure before merge
---
## Review Checklist (Critical)
| Check | Command/Method | Pass Criteria |
|-------|----------------|---------------|
| JSON Valid | `python3 -m json.tool file.json` | No syntax errors |
| All Checks Exist | Run validation script | 0 missing checks |
| No Duplicate IDs | Run validation script | 0 duplicate requirement IDs |
| Changelog fragment | Manual review | Fragment present under `prowler/changelog.d/` |
| Dashboard File | Compare with existing | Follows established pattern |
| Framework Metadata | Manual review | All required fields populated |
---
## Commands
```bash
# 1. Validate JSON syntax
python3 -m json.tool prowler/compliance/{provider}/{framework}.json > /dev/null \
&& echo "Valid JSON" || echo "INVALID JSON"
# 2. Run full validation script
python3 skills/prowler-compliance-review/assets/validate_compliance.py \
prowler/compliance/{provider}/{framework}.json
# 3. Compare dashboard with existing (find similar framework)
diff dashboard/compliance/{new_framework}.py \
dashboard/compliance/{existing_framework}.py
```
---
## Decision Tree
```text
JSON Valid?
├── No → FAIL: Fix JSON syntax errors
└── Yes ↓
All Checks Exist in Codebase?
├── Missing checks → FAIL: Add missing checks or remove from framework
└── All exist ↓
Duplicate Requirement IDs?
├── Yes → FAIL: Fix duplicate IDs
└── No ↓
Changelog Fragment Present?
├── No → REQUEST CHANGES: Add changelog fragment
└── Yes ↓
Dashboard File Follows Pattern?
├── No → REQUEST CHANGES: Fix dashboard pattern
└── Yes ↓
Framework Metadata Complete?
├── No → REQUEST CHANGES: Add missing metadata
└── Yes → APPROVE
```
---
## Framework Structure Reference
Compliance frameworks are JSON files in: `prowler/compliance/{provider}/{framework}.json`
```json
{
"Framework": "CIS",
"Name": "CIS Provider Benchmark vX.Y.Z",
"Version": "X.Y",
"Provider": "AWS|Azure|GCP|...",
"Description": "Framework description...",
"Requirements": [
{
"Id": "1.1",
"Description": "Requirement description",
"Checks": ["check_name_1", "check_name_2"],
"Attributes": [
{
"Section": "1 Section Name",
"SubSection": "1.1 Subsection (optional)",
"Profile": "Level 1|Level 2",
"AssessmentStatus": "Automated|Manual",
"Description": "...",
"RationaleStatement": "...",
"ImpactStatement": "...",
"RemediationProcedure": "...",
"AuditProcedure": "...",
"AdditionalInformation": "...",
"References": "...",
"DefaultValue": "..."
}
]
}
]
}
```
---
## Common Issues
| Issue | How to Detect | Resolution |
|-------|---------------|------------|
| Missing checks | Validation script reports missing | Add check implementation or remove from Checks array |
| Duplicate IDs | Validation script reports duplicates | Ensure each requirement has unique ID |
| Empty Checks for Automated | AssessmentStatus is Automated but Checks is empty | Add checks or change to Manual |
| Wrong file location | Framework not in `prowler/compliance/{provider}/` | Move to correct directory |
| Missing dashboard file | No corresponding `dashboard/compliance/{framework}.py` | Create dashboard file following pattern |
| Changelog fragment missing | No fragment file in the PR diff | Add a fragment under prowler/changelog.d/ |
---
## Dashboard File Pattern
Dashboard files must be in `dashboard/compliance/` and follow this exact pattern:
```python
import warnings
from dashboard.common_methods import get_section_containers_cis
warnings.filterwarnings("ignore")
def get_table(data):
aux = data[
[
"REQUIREMENTS_ID",
"REQUIREMENTS_DESCRIPTION",
"REQUIREMENTS_ATTRIBUTES_SECTION",
"CHECKID",
"STATUS",
"REGION",
"ACCOUNTID",
"RESOURCEID",
]
].copy()
return get_section_containers_cis(
aux, "REQUIREMENTS_ID", "REQUIREMENTS_ATTRIBUTES_SECTION"
)
```
---
## Testing the Compliance Framework
After validation passes, test the framework with Prowler:
```bash
# Verify framework is detected
uv run python prowler-cli.py {provider} --list-compliance | grep {framework}
# Run a quick test with a single check from the framework
uv run python prowler-cli.py {provider} --compliance {framework} --check {check_name}
# Run full compliance scan (dry-run with limited checks)
uv run python prowler-cli.py {provider} --compliance {framework} --checks-limit 5
# Generate compliance report in multiple formats
uv run python prowler-cli.py {provider} --compliance {framework} -M csv json html
```
---
## Resources
- **Validation Script**: See [assets/validate_compliance.py](assets/validate_compliance.py)
- **Related Skills**: See [prowler-compliance](../prowler-compliance/SKILL.md) for creating frameworks
- **Documentation**: See [references/review-checklist.md](references/review-checklist.md)
© prowler-cloud · Apache-2.0 · prowler-cloud/prowler