compliance-audit

Scan codebases for forbidden payment strings and PII exposure.

3|Updated Mar 26, 2026
One-click install
npx skills add https://github.com/The13thNode/VibeCorp_PromptCEO --skill compliance-audit-the13thnode
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: compliance-audit
Source: https://github.com/The13thNode/VibeCorp_PromptCEO/tree/main/skills/public/compliance-audit
Command: npx skills add https://github.com/The13thNode/VibeCorp_PromptCEO --skill compliance-audit-the13thnode

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill establishes a pre-task compliance audit and contextual rules to prevent sensitive or regulated functionality (payment processing, identity handling, contract flows) from being introduced or mishandled in a codebase, and to ensure proper masking, storage, and access gating for user data.

Core Features & Use Cases

  • Pre-commit/PR checklist: Grep-based checks for forbidden strings (stripe, escrow, DirectDebit, payment_intent) and placeholders to avoid reintroducing regulated files or routes.
  • Identity and PII rules: Guidance for masking PII fields in UI and ensuring KYC documents are stored in secure buckets only.
  • Verification tiers & access gating: Define tiered access patterns and enforce checks before exposing sensitive actions.
  • Domain-specific adapters: Example notes for property rental, healthcare, and financial services to adapt legal lane and occupancy or HIPAA rules.
  • Developer safety: Require zero TypeScript type errors (npx tsc --noEmit) before considering edits complete.

Quick Start

Load compliance-audit and run the checklist to scan for payment processing, forbidden files, PII exposures, secure storage issues, and tier gating before merging.

Frequently Asked Questions about compliance-audit

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

FAQPage Schema
How do I prevent PII leaks and unauthorized payment processing in my codebase?

Run a compliance audit to scan codebases for forbidden payment strings, verify masked PII display, enforce secure document storage, and gate access tiers before merging changes.

How do I check for forbidden payment strings during a PR review?

You can check for forbidden payment strings during a PR review by applying grep-based scans to identify regulated terms like escrow, DirectDebit, and payment_intent, ensuring no regulated routes or files are reintroduced into the codebase.

What is the best way to enforce identity verification tier gating for sensitive actions?

Enforce identity verification tier gating by defining tiered access patterns and applying verification checks before exposing sensitive actions or regulated contract flows.

Do I need zero TypeScript type errors before completing compliance checks?

Yes, compliance checks require zero TypeScript type errors via npx tsc --noEmit before considering edits complete, preventing type regressions alongside PII exposures.

Can I adapt compliance audit rules for healthcare or financial services domains?

Yes, compliance audit rules include domain-specific adapters to adjust legal lane rules, occupancy rules, or HIPAA requirements for property rental, healthcare, and financial services contexts.

Why should I run a compliance audit before adding identity verification features?

Run a compliance audit before adding identity verification features to verify secure KYC document storage, ensure masked PII display, and prevent mishandling of regulated user data.