wrdn-pii

Detect real personal identifiers and customer-confidential data in code changes.

56|3|Updated Apr 24, 2026
One-click install
npx skills add https://github.com/getsentry/warden-skills --skill wrdn-pii
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: wrdn-pii
Source: https://github.com/getsentry/warden-skills/tree/main/skills/wrdn-pii
Command: npx skills add https://github.com/getsentry/warden-skills --skill wrdn-pii

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Detects real personal identifiers and customer-confidential data introduced into code changes or exposed through unnecessary durable sinks.

Core Features & Use Cases

  • Identify real emails, customer org slugs, revenue or billing data, and other PII embedded in code, tests, fixtures, docs, or logs, and flag them for remediation.
  • Distinguish between real customer data and synthetic placeholders, so reviewers can focus on genuine privacy risks.
  • Generate actionable remediation guidance and support deterministic workflows during code review.

Quick Start

Run wrdn-pii against the changed files to surface any real customer identifiers.

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 leaks in code changes?

To detect real PII and customer data leaks in code changes, run this skill against modified files. It analyzes surrounding context to flag genuine personal identifiers and customer-confidential data introduced into tests, fixtures, docs, or logs.

How does code review distinguish real customer data from synthetic placeholders?

Code review distinguishes real customer data from synthetic placeholders by analyzing surrounding context, verifying exposure sinks, and evaluating identifier classes. This ensures reviewers focus on genuine privacy risks rather than fake test values.

What is the best way to find exposed customer identifiers in test fixtures and logs?

The best way to find exposed customer identifiers in test fixtures and logs is to scan changed files during code review. This identifies real emails, customer org slugs, and billing data embedded in unnecessary durable sinks.

Can I generate remediation guidance for privacy risks found in config and telemetry?

Yes, you can generate remediation guidance for privacy risks found in config and telemetry. The skill outputs findings with file/line numbers, identifier class, exposure sink, and severity to support deterministic remediation workflows.

Does this PII detection skill work on API responses and documentation?

Yes, this PII detection skill works on API responses and documentation. It is applied during code review across tests, fixtures, docs, config, telemetry, and API responses to surface real customer data leaks.