pii-and-compliance

Name: pii-and-compliance
Availability: InStock
Author: thrillmade

Flag code changes containing personally identifiable information in logs and error messages.

1|Updated May 15, 2026

Search Tags:#code review #security #PII detection #data compliance #logging review

Ready to run

npx skills add https://github.com/thrillmade/agent-skills --skill pii-and-compliance

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: pii-and-compliance
Source: https://github.com/thrillmade/agent-skills/tree/main/skills/pii-and-compliance
Command: npx skills add https://github.com/thrillmade/agent-skills --skill pii-and-compliance

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Prevents personally identifiable information (PII) from being accidentally logged or exposed in code.

Core Features & Use Cases

PII Detection: Identifies and flags instances where PII might be leaked.
Review Guidance: Provides detailed reasons and suggested fixes for identified issues.
Use Case: For a team working on an e-commerce application, this Skill ensures that sensitive user data like credit card numbers and personal details are not inadvertently stored in logs or exposed through error messages.

Quick Start

Review the flagged changes in your PR to ensure PII is not leaking.

Frequently Asked Questions about pii-and-compliance

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

FAQPage Schema

How do I detect PII leakage in code review?▼

PII leakage in code review is detected by analyzing log strings, error messages, and analytics events to flag exposed credit card numbers, emails, and personal details. This monitoring ensures compliance with data protection regulations by catching sensitive data before deployment.

What is PII detection in log strings and error messages?▼

PII detection in log strings and error messages is the process of monitoring code changes to identify and flag accidentally exposed personally identifiable information. It prevents sensitive user data like credit card numbers from being inadvertently stored in application logs.

How do I ensure data compliance for analytics events?▼

Data compliance for analytics events is ensured by reviewing flagged code changes to verify that PII is not leaking through event payloads. The process requires analyzing these events to confirm sensitive personal details are not exposed during data transmission.

Does this PII detection work with e-commerce application logs?▼

PII detection works with e-commerce application logs by scanning code changes to identify sensitive user data like credit card numbers and personal details. It ensures this information is not inadvertently stored in logs or exposed through error messages.

What is the best way to prevent credit card numbers from being logged?▼

The best way to prevent credit card numbers from being logged is to monitor code changes and flag instances where PII might be leaked in log strings. This approach provides detailed reasons and suggested fixes for identified compliance issues.