gdpr-scan

Scan source code for GDPR-sensitive personal data and generate markdown audit reports.

1|Updated Jan 13, 2023
One-click install
npx skills add https://github.com/theodrosyimer/.dotfiles --skill gdpr-scan
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gdpr-scan
Source: https://github.com/theodrosyimer/.dotfiles/tree/main/claude/skills/dev__gdpr-scan
Command: npx skills add https://github.com/theodrosyimer/.dotfiles --skill gdpr-scan

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Organizations need to ensure their codebases are free of GDPR‑sensitive personal data. Manual review is time‑consuming and error‑prone, risking non‑compliance and costly penalties.

Core Features & Use Cases

  • Calibration: Uses a seed catalog of known PII, safe, and watch‑list fields to guide scanning.
  • Comprehensive Scan: Globally searches domain events, commands, DTOs, and type definitions across the repository.
  • Risk Assessment: Evaluates PII exposure, module characteristics, and generates a detailed markdown audit.
  • Inventory Output: Produces gdpr-modules.json summarizing module classifications for downstream compliance tools.
  • Use Case: Run the skill on a micro‑service monorepo to automatically flag personal data leaks before release.

Quick Start

Run the gdpr-scan skill on your repository to produce a GDPR audit report.

Frequently Asked Questions about gdpr-scan

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I scan my codebase for GDPR-sensitive personal data?

Scan your codebase for GDPR-sensitive personal data by applying calibrated classification rules across domain events, commands, and DTOs. This process identifies PII exposure and produces a markdown audit report with a gdpr-modules.json inventory file for compliance analysis.

What is the best way to automate PII detection in a micro-service monorepo?

Automate PII detection in a micro-service monorepo by globally searching type definitions and domain events against a seed catalog of known PII and watch-list fields. This generates a detailed markdown audit and a gdpr-modules.json file summarizing module risk classifications.

Can I use this to flag personal data leaks before a release?

Yes, you can flag personal data leaks before release by running an automated scan across your repository. It evaluates PII exposure and generates a markdown audit report to help prevent non-compliance and costly penalties.

How does calibrated classification work for GDPR compliance scanning?

Calibrated classification works by using a seed catalog of known PII, safe, and watch-list fields to guide the scanning process. This calibration ensures accurate risk assessment of domain events and DTOs across your codebase.

What output formats are generated for GDPR compliance analysis?

The output formats generated for GDPR compliance analysis are a markdown audit report detailing PII exposure and risk assessment, alongside a gdpr-modules.json inventory file summarizing module classifications for downstream compliance tools.