Legal & compliance
comply
Compliance and governance — GDPR, HIPAA, SOC2, PCI-DSS, audit trails, privacy controls, data retention, license compliance.
arbazkhan971 · Static checks on file
Installation
Read the source and dependencies before running a command. Copying does not install or execute anything.
npx skills add arbazkhan971/godmode --skill complyAbout this skill
name: comply description: Compliance and governance — GDPR, HIPAA, SOC2, PCI-DSS, audit trails, privacy controls, data retention, license compliance.
Comply — Compliance & Governance
Activate When
- User invokes
/godmode:comply - User says "are we GDPR compliant?", "audit trail", "privacy review", "compliance check"
- Team builds features handling personal data, health data, or payment data
- Pre-ship check when
/godmode:shipdetects regulated data flows - User needs license compliance audit across dependencies
- Preparing for SOC2 audit or regulatory review
Workflow
Step 1: Define Compliance Scope
Determine which regulations and what code is in scope:
COMPLIANCE SCOPE:
Target: <feature/module/entire project>
Applicable regulations:
- [ ] GDPR (personal data of EU residents)
- [ ] HIPAA (protected health information)
- [ ] SOC2 (service organization controls)
- [ ] PCI-DSS (payment card data)
- [ ] CCPA (California consumer privacy)
- [ ] FERPA (educational records)
- [ ] Other: <specify>
Data classification:
Personal data: <files/modules handling PII>
Sensitive data: <files/modules handling health/financial/auth data>
Public data: <files/modules with non-sensitive data>
Step 2: GDPR Compliance Check
If personal data of EU residents is processed:
Lawful Basis
GDPR — LAWFUL BASIS ASSESSMENT:
| Data Processing Activity | Lawful Basis | Status |
|--|--|--|
| User registration | Consent | COMPLIANT |
| Order processing | Contract | COMPLIANT |
| Marketing emails | Consent | MISSING |
| Analytics tracking | Legitimate int. | REVIEW |
| Fraud detection | Legitimate int. | COMPLIANT |
Data Subject Rights
GDPR — DATA SUBJECT RIGHTS:
| Right | Implemented | Location |
|--|--|--|
| Right to access | YES/NO | <endpoint/UI> |
| Right to rectification | YES/NO | <endpoint/UI> |
| Right to erasure | YES/NO | <endpoint/UI> |
| Right to portability | YES/NO | <endpoint/UI> |
| Right to restrict proc. | YES/NO | <endpoint/UI> |
| Right to object | YES/NO | <endpoint/UI> |
| Automated decision-making | YES/NO/N/A | <endpoint/UI> |
Consent Management
CONSENT IMPLEMENTATION CHECK:
- [ ] Consent is freely given (not bundled with service access)
- [ ] Consent is specific (separate consent per purpose)
- [ ] Consent is informed (clear language, not legalese)
- [ ] Consent is unambiguous (affirmative action, no pre-ticked boxes)
- [ ] Consent is withdrawable (easy opt-out, same effort as opt-in)
- [ ] Consent records stored (who, when, what, version of terms)
- [ ] Under-16 users: parental consent mechanism exists
Step 3: HIPAA Compliance Check
If protected health information (PHI) is processed:
HIPAA — SAFEGUARDS ASSESSMENT:
| Safeguard | Status | Evidence |
ADMINISTRATIVE SAFEGUARDS
| Risk analysis conducted | YES/NO | <ref> |
|--|--|--|
| Workforce access controls | YES/NO | <ref> |
| Security awareness training | YES/NO | <ref> |
| Incident response procedures | YES/NO | <ref> |
| Business associate agreements | YES/NO | <ref> |
PHYSICAL SAFEGUARDS
| Facility access controls | YES/NO | <ref> |
|--|--|--|
| Workstation security | YES/NO | <ref> |
| Device and media controls | YES/NO | <ref> |
Step 4: SOC2 Compliance Check
If operating as a service organization:
SOC2 — TRUST SERVICES CRITERIA:
| Category | Controls | Implemented | Gaps |
|--|--|--|--|
| Security | 12 | <N> | <N> |
| Availability | 8 | <N> | <N> |
| Processing Integr. | 6 | <N> | <N> |
| Confidentiality | 7 | <N> | <N> |
| Privacy | 10 | <N> | <N> |
Key SOC2 Controls:
- [ ] Change management process documented and followed
- [ ] Logical access controls with least privilege
- [ ] Encryption in transit and at rest
- [ ] Monitoring and alerting for security events
- [ ] Incident response plan tested within last 12 months
Step 5: PCI-DSS Compliance Check
If payment card data is processed:
PCI-DSS — REQUIREMENTS CHECK:
| Requirement | Status |
|--|--|
| 1. Network security controls | PASS/FAIL |
| 2. Secure configuration | PASS/FAIL |
| 3. Protect stored account data | PASS/FAIL |
| 4. Encrypt transmission over networks | PASS/FAIL |
| 5. Protect from malicious software | PASS/FAIL |
| 6. Secure systems and software | PASS/FAIL |
| 7. Restrict access by business need | PASS/FAIL |
| 8. Identify users and auth access | PASS/FAIL |
| 9. Restrict physical access | PASS/FAIL/N/A |
| 10. Log and monitor all access | PASS/FAIL |
| 11. Test security regularly | PASS/FAIL |
Step 6: Audit Trail Design & Validation
Verify that all security and compliance events are logged:
AUDIT TRAIL ASSESSMENT:
| Event Category | Logged | Fields |
|--|--|--|
| Authentication | YES/NO | who, when, IP, result |
| Authorization changes | YES/NO | who, what, when, by-whom |
| Data access (read) | YES/NO | who, what, when |
| Data modification | YES/NO | who, what, old, new |
| Data deletion | YES/NO | who, what, when, reason |
| Data export | YES/NO | who, what, format, dest |
| Configuration changes | YES/NO | who, what, old, new |
| System errors | YES/NO | what, when, severity |
| Admin operations | YES/NO | who, what, when |
Step 7: Data Retention & Deletion
Verify data lifecycle management:
DATA RETENTION POLICY:
| Data Category | Retention | Auto-delete | Method |
|--|--|--|--|
| User accounts | Active+2y | YES/NO | <method> |
| Transaction logs | 7 years | YES/NO | <method> |
| Session data | 30 days | YES/NO | <method> |
| Audit logs | 3 years | YES/NO | <method> |
| Analytics data | 1 year | YES/NO | <method> |
| Backup data | 90 days | YES/NO | <method> |
| Temporary files | 24 hours | YES/NO | <method> |
Deletion workflow:
- [ ] Deletion request → verification → execution → confirmation
- [ ] Deletion cascades to all copies (backups, caches, replicas)
- [ ] Deletion is verifiable (can prove data no longer exists)
Step 8: License Compliance
Audit dependencies: MIT/Apache/BSD/ISC = safe. LG
Read the complete source ↗