prowler-compliance-review
Validates compliance framework JSON files and reviews PRs for security standards.
Install
mkdir -p .claude/skills/prowler-compliance-review && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/7923" && unzip -o skill.zip -d .claude/skills/prowler-compliance-review && rm skill.zipInstalls to .claude/skills/prowler-compliance-review
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
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.Key capabilities
- →Validate JSON syntax for compliance framework files
- →Check for missing or duplicate security requirement IDs
- →Verify framework metadata completeness
- →Compare new dashboard files against established patterns
- →Test compliance frameworks using Prowler CLI
How it works
The skill uses a validation script to check JSON structure and requirement IDs, followed by a manual review process for changelogs and dashboard patterns.
Inputs & outputs
When to use prowler-compliance-review
- →Validate JSON schema for compliance frameworks
- →Check for missing or duplicate security requirement IDs
- →Compare new framework dashboards with existing patterns
- →Automate PR reviews for CIS or NIST updates
About this skill
When to Use
- Reviewing PRs that add, extend or modify compliance frameworks under
prowler/compliance/ - Reviewing check-mapping changes,
ConfigRequirementsguardrails, or new compliance formatters
For authoring rules and the schema, load prowler-compliance.
Identify the schema first
| File | Schema | Expect in the PR |
|---|---|---|
prowler/compliance/<key>.json (top level, lowercase keys) | Universal | JSON only (+ optional UI mapper/panel/icon). No Python formatter, no COMPLIANCE_CLASS_MAP entry |
prowler/compliance/<provider>/<key>.json (Capitalized keys) | Legacy | JSON; plus formatter + __main__.py branch + COMPLIANCE_CLASS_MAP entry only if a new framework family/provider writer is introduced |
A brand-new framework submitted as legacy is a REQUEST CHANGES unless it extends an existing legacy family.
Review Checklist
| Check | How | Pass criteria |
|---|---|---|
| Loads | load_compliance_framework_universal() one-liner below | Not None (universal loader swallows errors, check the log) |
| Catalog integrity | uv run pytest tests/lib/check/compliance_catalog_integrity_test.py -k <basename> | Unique ids, no repeated checks, every check exists for its provider |
| Structure | validate_compliance.py <file> | No errors (both schemas) |
outputs.table_config (universal) | validator | Present, group_by declared in attributes_metadata |
attributes_metadata (universal) | read | Present, required/enum used for closed sets |
| Guardrails | read | Universal: Provider on every config_requirements entry. Value = strictest the control allows; ConfigKey exists in the check |
| Version | read | Set for versioned frameworks; filename version equals Version |
| Mapping quality | sample requirements vs check titles | Check literally verifies the requirement; otherwise [] (manual). No padding |
| Completeness | compare with source | Every source requirement present, including manual ones |
| Grouping values | jq '[.Requirements[].Attributes[0].Section] | unique' (legacy) | No spelling variants (they split the UI tree) |
| Tests | uv run pytest -n auto tests/lib/check/ tests/lib/outputs/compliance/ -q | Green |
| Changelog | PR diff | Fragment prowler/changelog.d/<slug>.<type>.md, no direct CHANGELOG.md edit |
Dashboard files (dashboard/compliance/<key with dots as underscores>.py) are optional: the local dashboard
falls back to dashboard/compliance/generic.py. Do not request one.
Commands
# Structure + check existence (legacy and universal)
python3 skills/prowler-compliance-review/assets/validate_compliance.py prowler/compliance/<path>.json
# Load with the real model (prints framework, requirement count, providers)
uv run python -c "from prowler.lib.check.compliance_models import load_compliance_framework_universal as l; \
fw=l('prowler/compliance/<path>.json'); assert fw, 'see log'; print(fw.framework, len(fw.requirements), fw.get_providers())"
# Repo integrity tests for this file
uv run pytest tests/lib/check/compliance_catalog_integrity_test.py -k "<basename>" -q
# CLI: listed and requirements visible (no credentials needed)
uv run python prowler-cli.py <provider> --list-compliance | grep <key>
uv run python prowler-cli.py <provider> --list-compliance-requirements <key>
# Full run against a real account (writes output/compliance/)
uv run python prowler-cli.py <provider> --compliance <key> -M csv json-ocsf html
--compliance cannot be combined with --check, --service, --checks-file or --category (mutually
exclusive argparse group).
Decision Tree
Loads with the real model? No -> FAIL
Integrity test / validator errors? Yes -> FAIL (missing checks, duplicate ids, missing table_config...)
New framework authored as legacy? Yes -> REQUEST CHANGES (use universal) unless extending a legacy family
Mappings padded or requirements missing? Yes -> REQUEST CHANGES
Changelog fragment missing? Yes -> REQUEST CHANGES
Otherwise -> APPROVE
Common Issues
| Issue | Detect | Resolution |
|---|---|---|
| Typo in check id | integrity test / validator | Fix id or remove it |
Universal file without table_config | validator | Add outputs.table_config.group_by |
| Unknown attribute key | loader returns None, log says unknown attribute | Declare it in attributes_metadata or fix the key |
Uppercase provider key in checks | validator | Use prowler/providers/ directory names |
Guardrail without Provider in universal file | validator | Add Provider |
| Automated requirement with no checks (CIS-style) | validator warning | Add checks or mark Manual |
Manual edit of CHANGELOG.md | diff | Move to a changelog.d fragment |
Resources
- Validator: assets/validate_compliance.py
- Summary template and file locations: references/review-checklist.md
- Authoring skill: prowler-compliance
- Docs:
docs/developer-guide/security-compliance-framework.mdx
When not to use it
- →Reviewing non-compliance related pull requests
Prerequisites
Limitations
- →Requires manual review of changelog fragments
- →Dashboard files must follow a specific Python pattern
How it compares
It automates the validation of compliance framework structure and metadata, which would otherwise require manual verification against the codebase.
Compared to similar skills
prowler-compliance-review side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| prowler-compliance-review (this skill) | 0 | 5mo | Review | Advanced |
| fix-dependabot-alerts | 18 | 9mo | Review | Intermediate |
| semgrep-rule-variant-creator | 1 | 5mo | Review | Advanced |
| hooks-system | 1 | 9mo | Review | Advanced |
Try saying
Example prompts that trigger this skill in your AI assistant.
More by prowler-cloud
View all by prowler-cloud →You might also like
fix-dependabot-alerts
microsoft
Fix Dependabot security alerts by updating vulnerable npm dependencies. Use when the user mentions "dependabot", "security alerts", "vulnerability", "CVE", or wants to update packages with security issues.
semgrep-rule-variant-creator
trailofbits
Creates language variants of existing Semgrep rules. Use when porting a Semgrep rule to specified target languages. Takes an existing rule and target languages as input, produces independent rule+test directories for each language.
hooks-system
MadAppGang
Comprehensive lifecycle hook patterns for Claude Code workflows. Use when configuring PreToolUse, PostToolUse, UserPromptSubmit, Stop, or SubagentStop hooks. Covers hook matchers, command hooks, prompt hooks, validation, metrics, auto-formatting, and security patterns. Trigger keywords - "hooks", "PreToolUse", "PostToolUse", "lifecycle", "tool matcher", "hook template", "auto-format", "security hook", "validation hook".
moai-workflow-loop
modu-ai
Ralph Engine - Automated feedback loop with LSP diagnostics and AST-grep integration for continuous code quality improvement. Use when implementing error-driven development, automated fixing, or continuous quality validation workflows.
yes
sstklen
Use when any task involves modifying files, configs, databases, or deployments. Use when debugging hits 2+ failures. Use when about to guess or assume without evidence ('probably', 'might be', 'I think', 'should be'). Use when deflecting to user ('please check...', 'you should manually...', 'you may
1password
openclaw
Set up and use 1Password CLI (op). Use when installing the CLI, enabling desktop app integration, signing in (single or multi-account), or reading/injecting/running secrets via op.