Stats
Actions
Tags
From compliance-pilot
Fixes open compliance findings by spawning remediator agents that propose changes, capture evidence, require human approval, apply fixes, and verify with Prowler re-checks. Use for single IDs, all open, or severity-filtered batches.
How this skill is triggered — by the user, by Claude, or both
Slash command
/compliance-pilot:remediateThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Fix open compliance findings identified by the scanner.
Fix open compliance findings identified by the scanner.
If $ARGUMENTS contains a specific finding ID (e.g., FINDING-s3-a1b2c3d4):
Use the Agent tool to spawn a single remediator agent:
subagent_type: remediatorIf $ARGUMENTS is all or empty:
.compliance/findings/FINDING-*.jsonstatus is open--severity if provided in argumentssubagent_type: remediatorIf $ARGUMENTS contains --severity critical,high:
/remediate # Remediate all open findings
/remediate FINDING-s3-a1b2c3d4 # Fix one specific finding
/remediate all # Same as no args
/remediate --severity critical # Only critical findings
/remediate --severity critical,high # Critical and high
For each finding, the remediator will:
After all remediations, show a summary of what was fixed.
npx claudepluginhub prajapatimehul/comp-agent --plugin compliance-pilotMakes cloud accounts compliant with security/industry frameworks via iterative Prowler Cloud setup, reporting, and remediation. Handles provider configuration, framework selection, and step-by-step compliance checking.
Guides privacy audit findings remediation: prioritizes by severity (critical, high, medium, low), assigns owners, tracks deadlines, verifies fixes, applies closure criteria, and escalates overdue items.
Applies a deterministic remediation patch for a specific security scanner finding via MCP toolchain (synthesize→verify→apply). Handles single-finding and batch fixes with HMAC-verified writes and project test verification.