compliance-governance

Implement GDPR/SOC2 compliance controls for PII detection, consent, DSAR, audit logging, and retention.

16|Updated Apr 30, 2026
One-click install
npx skills add https://github.com/JCETools-Petra/JCE-Opencode-Tools --skill compliance-governance-jcetools-petra
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: compliance-governance
Source: https://github.com/JCETools-Petra/JCE-Opencode-Tools/tree/main/config/skills/compliance-governance
Command: npx skills add https://github.com/JCETools-Petra/JCE-Opencode-Tools --skill compliance-governance-jcetools-petra

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps implement GDPR/SOC2-style compliance by governing PII handling, consent management, audit logging, and data retention so engineering work can be reviewed and verified with evidence.

Core Features & Use Cases

  • PII detection & protection: Identify direct/indirect PII and prevent common leak paths like logging PII or placing PII in query parameters.
  • Consent & DSAR workflows: Implement consent grant/revoke logic and support DSAR access/erasure patterns with deadlines and audit evidence.
  • Audit logging & retention automation: Use append-only audit entries and define retention policies per data type for ongoing enforcement.

Quick Start

Use the compliance-governance skill to review and implement GDPR-compliant consent, DSAR (access + erasure), retention, and append-only audit logging for the feature you are building.

Frequently Asked Questions about compliance-governance

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

FAQPage Schema
How do I implement GDPR DSAR access and erasure workflows with audit evidence?

To implement GDPR DSAR access and erasure, apply consent grant and revoke logic, support data subject access requests with deadlines, and generate append-only audit logs as verifiable compliance evidence.

What is the best way to prevent PII from leaking into query parameters and logs?

Preventing PII leaks requires identifying direct and indirect PII fields, blocking PII from query parameters, and applying append-only audit logging with built-in PII redaction to ensure safe handling.

How do I automate data retention enforcement for SOC2 compliance?

Automating data retention for SOC2 involves defining per-data-type retention policies and executing automated retention actions with measurable outcomes to maintain ongoing compliance enforcement.

Does this approach support privacy by design and consent withdrawal proof?

Yes, this approach supports privacy by design by governing PII handling and provides consent proof and withdrawal mechanisms, ensuring software engineering tasks meet GDPR and SOC2 review requirements.

When do I need PII detection and classification for compliance checklists?

You need PII detection and classification when building features that touch privacy policies, requiring data inventory, field classification, and compliance verification via checklists and evidence.

Why should I use append-only audit logging for privacy-related debugging?

Append-only audit logging ensures immutable records for privacy-related debugging by redacting PII, capturing consent proof, and providing the evidence needed to verify compliance controls.