Skip to main content
skill CX Codex

compliance-testing · proffesor-for-testing — Claude Code skill: GDPR, HIPAA, PCI-DSS testing

compliance-testing is a skill that checks an app against GDPR, CCPA, HIPAA, SOC2, and PCI-DSS, and tests user rights, encryption, and access logs before audits or during work with personal data.

MIT 1 installs ★ 533 updated 2026-10-25

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add proffesor-for-testing/agentic-qe --skill compliance-testing -a claude-code
Open on GitHub

What compliance-testing does

compliance-testing checks core regulatory requirements: user data rights (access, deletion, portability), encryption at rest and in transit, access logging for PII/PHI, and timestamped consent tracking. It includes ready-made tests for GDPR (account export and deletion, consent verification), HIPAA (PHI encryption, physician access logs), and PCI-DSS (payment card data tokenization only, no storage of full numbers).

The skill runs through agents: qe-security-scanner scans for vulnerabilities, qe-test-executor runs compliance tests, qe-quality-gate blocks non-compliant releases. Output is audit-ready reports with evidence for each control. Violations carry heavy penalties: GDPR up to €20M or 4% of revenue, HIPAA up to $1.5M per violation, PCI-DSS $100k per month.

You'll need npm and database access to your application so the skill can verify encryption state and audit logs. Tests are written in JavaScript and work with any REST API-based project.

What it helps with

  • verify user data is fully deleted when requested
  • ensure payment card numbers are never stored in the database
  • log every access to medical records with timestamps
  • validate consent is captured before collecting personal data
  • generate audit evidence for GDPR compliance review

Example prompts for the agent

  • Test whether the app meets GDPR and PCI-DSS requirements
  • Run a full compliance audit before release
  • Validate user data rights: export, deletion, and portability

How to install compliance-testing

1Skills CLI (Vercel)

npx skills add proffesor-for-testing/agentic-qe --skill compliance-testing -a claude-code

2Manually: put the files in place

~/.claude/skills/compliance-testing/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/compliance-testing/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about compliance-testing

How do I install compliance-testing in Claude Code?

Run npx skills add proffesor-for-testing/agentic-qe --skill compliance-testing -a claude-code, then open ~/.claude/skills/compliance-testing/SKILL.md to verify.

What does compliance-testing do?

It tests your app against GDPR, CCPA, HIPAA, SOC2, and PCI-DSS: verifies user rights (data export, deletion), validates encryption and access logging for sensitive data, tracks consent with timestamps and IP addresses.

Which regulations does this skill cover?

GDPR (EU data protection), CCPA (California consumer rights), HIPAA (healthcare data), PCI-DSS (payment card security), and SOC2 (SaaS security controls).

Source text

SKILL.md · MIT
---
name: compliance-testing
description: "Regulatory compliance testing for GDPR, CCPA, HIPAA, SOC2, PCI-DSS and industry-specific regulations. Use when ensuring legal compliance, preparing for audits, or handling sensitive data."
category: specialized-testing
priority: high
tokenEstimate: 900
agents: [qe-security-scanner, qe-test-executor, qe-quality-gate]
implementation_status: optimized
optimization_version: 1.0
last_optimized: 2025-12-02
dependencies: []
quick_reference_card: true
tags: [compliance, gdpr, hipaa, pci-dss, ccpa, soc2, privacy, audit]
# ADR-056 Validation Stack Configuration
trust_tier: 3
validation:
  schema_path: schemas/output.json
  validator_path: scripts/validate-config.json
  eval_path: evals/compliance-testing.yaml
---

# Compliance Testing

<default_to_action>
When validating regulatory compliance:
1. IDENTIFY applicable regulations (GDPR, HIPAA, PCI-DSS, etc.)
2. MAP requirements to testable controls
3. TEST data rights (access, erasure, portability)
4. VERIFY encryption and access logging
5. GENERATE audit-ready reports with evidence

**Quick Compliance Checklist:**
- Data subject rights work (access, delete, export)
- PII is encrypted at rest and in transit
- Access to sensitive data is logged
- Consent is tracked with timestamps
- Payment card data not stored (only tokenized)

**Critical Success Factors:**
- Non-compliance = €20M or 4% revenue (GDPR)
- Audit trail everything
- Test continuously, not just before audits
</default_to_action>

## Quick Reference Card

### When to Use
- Legal compliance requirements
- Before security audits
- Handling PII/PHI/PCI data
- Entering new markets (EU, CA, healthcare)

### Major Regulations
| Regulation | Scope | Key Focus |
|------------|-------|-----------|
| **GDPR** | EU data | Privacy rights, consent |
| **CCPA** | California | Consumer data rights |
| **HIPAA** | Healthcare | PHI protection |
| **PCI-DSS** | Payments | Card data security |
| **SOC2** | SaaS | Security controls |

### Penalties
| Regulation | Maximum Fine |
|------------|--------------|
| **GDPR** | €20M or 4% revenue |
| **HIPAA** | $1.5M per violation |
| **PCI-DSS** | $100k/month |
| **CCPA** | $7,500 per violation |

---

## GDPR Compliance Testing

```javascript
// Test data subject rights
test('user can request their data', async () => {
  const response = await api.post('/data-export', { userId });

  expect(response.status).toBe(200);
  expect(response.data.downloadUrl).toBeDefined();

  const data = await downloadFile(response.data.downloadUrl);
  expect(data).toHaveProperty('profile');
  expect(data).toHaveProperty('orders');
});

test('user can delete their account', async () => {
  await api.delete(`/users/${userId}`);

  // All personal data deleted
  expect(await db.users.findOne({ id: userId })).toBeNull();
  expect(await db.orders.find({ userId })).toHaveLength(0);

  // Audit log retained (legal requirement)
  expect(await db.auditLogs.find({ userId })).toBeDefined();
});

test('consent is tracked', async () => {
  await api.post('/consent', {
    userId, type: 'marketing', granted: true,
    timestamp: new Date(), ipAddress: '192.168.1.1'
  });

  const consent = await db.consents.findOne({ userId, type: 'marketing' });
  expect(consent.timestamp).toBeDefined();
  expect(consent.ipAddress).toBeDefined();
});
```

---

## HIPAA Compliance Testing

```javascript
// Test PHI security
test('PHI is encrypted at rest', async () => {
  const patient = await db.patients.create({
    ssn: '123-45-6789',
    medicalHistory: 'Diabetes'
  });

  const raw = await db.raw('SELECT * FROM patients WHERE id = ?', patient.id);
  expect(raw.ssn).not.toBe('123-45-6789'); // Should be encrypted
});

test('access to PHI is logged', async () => {
  await api.get('/patients/123', {
    headers: { 'User-Id': 'doctor456' }
  });

  const auditLog = await db.auditLogs.findOne({
    resourceType: 'patient',
    resourceId: '123',
    userId: 'doctor456'
  });

  expect(auditLog.action).toBe('read');
  expect(auditLog.timestamp).toBeDefined();
});
```

---

## PCI-DSS Compliance Testing

```javascript
// Test payment card handling
test('credit card numbers not stored', async () => {
  await api.post('/payment', {
    cardNumber: '4242424242424242',
    expiry: '12/25', cvv: '123'
  });

  const payment = await db.payments.findOne({ /* ... */ });
  expect(payment.cardNumber).toBeUndefined();
  expect(payment.last4).toBe('4242'); // Only last 4
  expect(payment.tokenId).toBeDefined(); // Token from gateway
});

test('CVV never stored', async () => {
  const payments = await db.raw('SELECT * FROM payments');
  const hasCVV = payments.some(p =>
    JSON.stringify(p).toLowerCase().includes('cvv')
  );
  expect(hasCVV).toBe(false);
});
```

---

## Agent-Driven Compliance

```typescript
// Comprehensive compliance validation
await Task("Compliance Validation", {
  regulations: ['GDPR', 'PCI-DSS'],
  scope: 'full-application',
  generateAuditReport: true
}, "qe-security-scanner");

// Returns:
// {
//   gdpr: { compliant: true, controls: 12, passed: 12 },
//   pciDss: { compliant: false, controls: 8, passed: 7 },
//   violations: [{ control: 'card-storage', severity: 'critical' }],
//   auditReport: 'compliance-audit-2025-12-02.pdf'
// }
```

---

## Agent Coordination Hints

### Memory Namespace
```
aqe/compliance-testing/
├── regulations/*        - Regulation requirements
├── controls/*           - Control test results
├── audit-reports/*      - Generated audit reports
└── violations/*         - Compliance violations
```

### Fleet Coordination
```typescript
const complianceFleet = await FleetManager.coordinate({
  strategy: 'compliance-validation',
  agents: [
    'qe-security-scanner',   // Scan for vulnerabilities
    'qe-test-executor',      // Execute compliance tests
    'qe-quality-gate'        // Block non-compliant releases
  ],
  topology: 'sequential'
});
```

---

## Related Skills
- [security-testing](../security-testing/) - Security vulnerabilities
- [test-data-management](../test-data-management/) - PII handling
- [accessibility-testing](../accessibility-testing/) - Legal requirements

---

## Remember

**Compliance is mandatory, not optional.** Fines are severe: GDPR up to €20M or 4% of revenue, HIPAA up to $1.5M per violation. But beyond fines, non-compliance damages reputation and user trust.

**Audit trail everything.** Every access to sensitive data, every consent, every deletion must be logged with timestamps and user IDs.

**With Agents:** Agents validate compliance requirements continuously, detect violations early, and generate audit-ready reports. Catch compliance issues in development, not in audits.

## Gotchas

- Agent checks GDPR consent flow but misses data retention — always verify deletion/anonymization actually works
- Compliance reports with "100% compliant" are suspicious — no real system is fully compliant, verify each claim
- Agent may test US regulations only — explicitly specify jurisdiction (EU, CA, etc.) for correct requirements
- PII in test data is itself a compliance violation — never use production PII, use synthetic generators
- Audit trail gaps are invisible until audit time — verify logging exists for EVERY data access, not just writes

© proffesor-for-testing · MIT · proffesor-for-testing/agentic-qe

Similar skills

All skills for Testing and QA →

compliance-testing by other authors comes first.

compliance-testing kindlmann compliance-testing — a skill that tests how your site handles consent: what loads before a click, what survives a rejection. CX Codex +1 1,300installs compliance-checker OneWave-AI The compliance-checker skill audits codebases and business processes against GDPR, HIPAA, SOC2, CCPA, and PCI-DSS. Use it to find control gaps and build a compliance report. CX Codex +1 257installs compliance-tracking official anthropics compliance-tracking tracks compliance requirements and audit readiness across SOC 2, ISO 27001, GDPR, HIPAA and PCI DSS, helping structure control data for upcoming audits. CX Codex +1 3,100installs data-privacy-compliance davila7 data-privacy-compliance provides implementation blueprints for GDPR, CCPA, and HIPAA compliance directly in your codebase. CX Codex +1 259installs agency-legal-compliance-checker huytran1120 agency-legal-compliance-checker is a Claude Code skill that audits business workflows and product features against legal and privacy regulations. Evaluates GDPR, CCPA, and HIPAA requirements. CX Codex +1 ★ 85repo stars security-compliance-compliance-check sickn33 security-compliance-compliance-check guides regulatory compliance checks for GDPR, HIPAA, SOC2, and PCI-DSS, generating gap analyses, checklists, and technical control code. CX Codex +1 ★ 50,109repo stars compliance-check Seth Hobson compliance-check works out which regulations apply to your product and points at the controls you still need before an audit. CX Codex +1 ★ 42,780repo stars

From the same set73

The whole set →
qcsd-cicd-swarm The qcsd-cicd-swarm Claude Code skill checks CI/CD pipelines before release and assesses deployment readiness. It reviews regression risk and flaky tests, then returns a RELEASE, REMEDIATE, or BLOCK decision. CX Codex +1 104installs test-idea-rewriting test-idea-rewriting is a Claude Code skill that turns passive test descriptions into active actions with observable results. It runs when test ideas are vague or fail quality validation. CX Codex +1 104installs cicd-pipeline-qe-orchestrator The cicd-pipeline-qe-orchestrator skill assigns quality checks and QE agents to CI/CD stages, from commit through production. Use it to plan pipeline testing and define release gates. CX Codex +1 1installs accessibility-testing accessibility-testing — a skill with checklists and test snippets for checking keyboard navigation, color contrast and screen reader support against WCAG 2.2. CX Codex +1 1installs qe-visual-accessibility qe-visual-accessibility runs WCAG 2.2 accessibility audits and catches UI regressions through pixel-diff screenshot comparisons. It validates responsive layouts after CSS or component changes. CX Codex +1 1installs exploratory-testing-advanced exploratory-testing-advanced is a Claude Code skill for planning exploratory sessions, investigating bugs, and recording defects. It supports checks of new features and issues automated tests miss. CX Codex +1 1installs quality-metrics Tracks software quality metrics like defect density, DORA indicators, MTTD, and bug escape rates for CI quality gates. CX Codex +1 1installs bug-reporting-excellence The bug-reporting-excellence skill guides an agent through clear bug reports with reproduction steps, environment details, and impact. Use it when documenting defects or setting reporting standards for a team. CX Codex +1 1installs

Project sponsors

Companies that keep this analytics open