Stats
Actions
Tags
From code-audit-suite
This skill should be used when the user asks to "run Bearer", "scan for PII", "Datenschutz prüfen", "DSGVO/GDPR check", "find sensitive data flows", "PII/PHI scan", "privacy risk", or wants to know where personal/health data flows through the code. Runs Bearer in Docker to classify and trace sensitive data, processed directly in Claude Code.
How this skill is triggered — by the user, by Claude, or both
Slash command
/code-audit-suite:bearer-privacyThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Bearer adds a dimension orthogonal to SonarQube and the pure taint engines: it
Bearer adds a dimension orthogonal to SonarQube and the pure taint engines: it classifies 120+ sensitive data types (PII/PHI) and traces where that data flows — a privacy/GDPR (DSGVO) lens, not just vulnerability classes. It answers "does personal data reach a log, a third-party API, or an unencrypted store?", which neither SonarQube nor a generic SAST tool reports.
This is unique coverage, not a duplicate of any other skill.
~/.claude/skills/bearer-privacy/scripts/scan.sh [TARGET_DIR]
sast (security + privacy rules). BEARER_SCANNER=secrets
runs Bearer's secret detection instead — prefer the dedicated secrets-scan
skill for that.BEARER_SEVERITY (default
critical,high); review medium/low informationally.BEARER_FORMAT=json scan.sh [DIR].scripts/scan.sh — runs bearer scan against a directory, exit 1 on
findings at/above the severity threshold. Env: BEARER_FORMAT,
BEARER_SCANNER, BEARER_SEVERITY.npx claudepluginhub mguttmann/code-audit-suite --plugin code-audit-suiteProvides CDSS development patterns for drug interaction checking, dose validation, clinical scoring (NEWS2, qSOFA), and alert classification integrated into EMR workflows.