compliance-checker — Claude Code skill: audit and install
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.
MIT 257 installs ★ 440 updated 2026-10-20
npx skills add OneWave-AI/claude-skills --skill compliance-checker -a claude-codeWhat compliance-checker does
compliance-checker examines seven areas: personal data, retention, encryption, access control, audit logs, consent, and data transfers. It can inspect application code, database schemas, infrastructure settings, CI/CD files, dependency manifests, documentation, and environment configuration. The result is written to compliance-report.md in the project root or another path you provide.
The skill works with Read, Glob, Grep, Bash, and Write. Its supporting files cover framework requirements, search patterns, status and risk rules, cross-framework mappings, and the report layout. Findings include file paths, line numbers, severity, remediation steps, and evidence requirements. Technical controls cannot be verified without access to the project.
You can target one framework or one scan category. When reviewing business-process documents, the skill separates organizational controls from checks that require code or infrastructure access.
What it helps with
- audit a codebase against GDPR and related frameworks
- locate handling of personal or payment data
- map control gaps to regulatory requirements
- produce remediation steps and evidence requirements
Example prompts for the agent
- Audit this project against GDPR and write
compliance-report.md. - Check PCI-DSS, focusing on encryption and access control.
- Review this business-process documentation for HIPAA and list controls that need code-level verification.
How to install compliance-checker
1Skills CLI (Vercel)
npx skills add OneWave-AI/claude-skills --skill compliance-checker -a claude-code2Manually: put the files in place
~/.claude/skills/compliance-checker/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/compliance-checker/
1Skills CLI (Vercel)
npx skills add OneWave-AI/claude-skills --skill compliance-checker -a codex2Manually: put the files in place
.agents/skills/compliance-checker/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add OneWave-AI/claude-skills --skill compliance-checker -a cursor2Manually: put the files in place
.cursor/skills/compliance-checker/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install OneWave-AI/claude-skills compliance-checker2Manually: put the files in place
.github/skills/compliance-checker/SKILL.md1Skills CLI (Vercel)
npx skills add OneWave-AI/claude-skills --skill compliance-checker -a gemini-cli2Platform CLI
gemini skills install https://github.com/OneWave-AI/claude-skills --path compliance-checkerManually: put the files in place
.devin/skills/compliance-checker/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add OneWave-AI/claude-skills --skill compliance-checker -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 compliance-checker
How do I install compliance-checker in Claude Code?
Run npx skills add OneWave-AI/claude-skills --skill compliance-checker -a claude-code, then open ~/.claude/skills/compliance-checker/SKILL.md.
What does compliance-checker do?
It scans a codebase or business process across seven control areas, maps observations to GDPR, HIPAA, SOC2, CCPA, and PCI-DSS, and creates compliance-report.md with remediation and evidence requirements.
How does the skill handle controls it cannot verify?
It does not invent findings. When evidence is missing, it marks the item UNABLE TO ASSESS, and it distinguishes organizational controls from technical checks that require project access.
Source text
SKILL.md · MIT
--- name: compliance-checker description: Audits a codebase or business process for regulatory compliance across GDPR, HIPAA, SOC2, CCPA, and PCI-DSS. Scans for PII handling, data retention, encryption, access controls, audit logging, consent management, and data transfer issues. Generates a structured compliance report with findings, gap analysis, remediation steps, and evidence requirements. tools: Read, Glob, Grep, Bash, Write model: inherit --- # Compliance Checker Perform thorough regulatory compliance audits against one or more frameworks, identify gaps, and produce actionable remediation guidance with evidence requirements suitable for certification preparation. ## Contents - `references/frameworks.md` — the five supported frameworks (GDPR, HIPAA, SOC 2, CCPA, PCI-DSS): scope, key articles/requirements, penalties, and reference links. - `references/scan-patterns.md` — the seven scan categories, their search patterns, scan execution rules, and common pitfalls to always check. - `references/classification.md` — compliance status values, risk severity rubric, and the remediation detail fields. - `references/cross-framework-mapping.md` — control-area-to-framework mapping and the glossary. - `references/output-template.md` — the full `compliance-report.md` structure, including per-framework gap-analysis tables and evidence packs. ## Workflow Run the full methodology for every audit. Do not skip steps. ### Phase 1: Discovery and Scoping 1. Identify the target: codebase, infrastructure configuration, business process documentation, or a combination. 2. Determine applicable frameworks from the data types processed, geographic scope, industry, and business model. See `references/frameworks.md`. When none are specified, assess all five and note applicability. 3. Map the data flow: where regulated data enters, how it is processed, where it is stored, and how it exits. 4. Inventory data categories present (PII, PHI, CHD, sensitive PI, special category data). ### Phase 2: Scanning and Evidence Collection 5. Scan each of the seven categories — PII/sensitive data, data retention, encryption, access controls, audit logging, consent management, and data transfer. Apply the search patterns and execution rules in `references/scan-patterns.md`. Record exact file paths, line numbers, and snippets for both positive findings and gaps. ### Phase 3: Gap Analysis 6. Map each finding to specific framework requirements, assign a compliance status, and assign a risk severity to every non-compliant or partial finding. Use the rubric in `references/classification.md`. ### Phase 4: Remediation Planning 7. For each non-compliant or partial finding, produce the remediation detail (description, regulatory reference, current state, required state, steps, evidence, effort, dependencies) per `references/classification.md`. Cross-reference `references/cross-framework-mapping.md` to flag when one action closes gaps across multiple frameworks. ### Phase 5: Report Generation 8. Generate `compliance-report.md` in the project root (or a user-specified location), following the mandatory structure in `references/output-template.md`. Every section is required; if a section has no findings, state that explicitly. ## Behavioral Rules 1. Never fabricate findings. Back every finding with scan evidence. When evidence is absent, mark UNABLE TO ASSESS rather than guess. 2. Be specific. Reference exact file paths, line numbers, function names, and configuration keys. 3. Distinguish technical from organizational controls. Note when a finding requires verifying organizational controls (training, policies, physical security) that code review alone cannot confirm. 4. Consider the full stack: application code, database schemas, infrastructure configuration, CI/CD pipelines, dependency manifests, documentation, and environment configuration. 5. Prioritize actionable findings. Specify exact changes; avoid vague recommendations like "improve security". 6. Respect the scope. Audit only what is provided. Do not assume broader infrastructure without evidence. 7. Account for frameworks and libraries that handle compliance concerns (ORM parameterized queries, framework CSRF protection); credit them as positive findings but verify configuration. 8. Avoid false positives. Missing a marginal finding is better than reporting a non-gap. Err toward accuracy. 9. Cross-reference across frameworks. Note when a single remediation addresses multiple regulations. 10. Date and version everything so the report can be compared against future audits. ## Responding to Requests - "Audit this codebase" / "check compliance": Confirm which frameworks to focus on (or assess all five), run Phases 1-5, generate `compliance-report.md`, and summarize the most critical findings. - "Check for [framework]": Focus on that framework, still scan all seven categories, and map findings only to it. - "Check [category]" (e.g., "check encryption"): Focus the scan on that category and map findings to all applicable frameworks. - "Are we [requirement] compliant?" (e.g., GDPR Art. 17): Focus on the relevant controls, give a direct assessment with evidence, and offer remediation if gaps exist. - Business process documentation instead of code: Adapt the methodology to document analysis, focus on policy and procedure requirements, and note that technical controls cannot be verified without codebase access.
© OneWave-AI · MIT · OneWave-AI/claude-skills