wrdn-pii

Detect real PII and customer-confidential data in code changes, logs, and telemetry.

6|1|Updated Nov 23, 2023
One-click install
npx skills add https://github.com/gmcabrita/dotfiles --skill wrdn-pii-gmcabrita
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: wrdn-pii
Source: https://github.com/gmcabrita/dotfiles/tree/main/.agents/skills/wrdn-pii
Command: npx skills add https://github.com/gmcabrita/dotfiles --skill wrdn-pii-gmcabrita

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Identifies real PII and customer-confidential data that leaks into code changes, fixtures, docs, logs, or telemetry.

Core Features & Use Cases

  • Detects real emails, customer slugs, revenue data, and other identifiers in code and docs.
  • Distinguishes fake data, placeholders, and author metadata to reduce false positives.
  • Use cases include PR diffs, test fixtures, logs, and API responses where sensitive data might be exposed.

Quick Start

Analyze the most recent diff to locate and redact any real customer data before review.

Frequently Asked Questions about wrdn-pii

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

FAQPage Schema
How do I detect real PII and customer data hidden in code changes and logs?

To detect real PII in code changes and logs, you analyze source files, test fixtures, and telemetry to identify actual emails or customer slugs while excluding placeholders and synthetic data.

How does PII detection distinguish between real customer data and fake placeholders in test fixtures?

PII detection distinguishes fake data from real data by enforcing a trace-first evaluation that requires a concrete data class and a defined exposure sink, actively excluding author metadata, placeholders, and synthetic data to reduce false positives.

What is the best way to scan pull request diffs for sensitive data exposure before review?

Scanning pull request diffs for sensitive data exposure involves analyzing the most recent code changes to locate and redact any real customer data, checking source files, configuration, documentation, and API responses.

Can I use automated redaction to find customer-confidential data in API responses and telemetry?

Yes, you can apply automated redaction to API responses and telemetry by identifying real PII and customer-confidential data, requiring a concrete data class and a defined exposure sink for accurate detection.

Does PII detection in source files work for revenue data and customer slugs?

Yes, PII detection in source files works for revenue data and customer slugs by evaluating code changes, configuration, and documentation to locate real identifiers exposed in defined sinks.