des-persona-governance-reviewer

Evaluate data lineage, metadata stewardship, access control, and privacy handling for governance compliance.

2|Updated May 20, 2026
One-click install
npx skills add https://github.com/DKSang/DES-SKILL --skill des-persona-governance-reviewer
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: des-persona-governance-reviewer
Source: https://github.com/DKSang/DES-SKILL/tree/main/skills/des-persona-governance-reviewer
Command: npx skills add https://github.com/DKSang/DES-SKILL --skill des-persona-governance-reviewer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It resolves governance gaps that can cause sensitive data exposure, broken lineage traceability, and non-compliant metadata, access control, and retention handling across a data engineering lifecycle.

Core Features & Use Cases

  • Governance and security decisioning for sensitive data: Reviews PII classification, masking/tokenization/encryption choices, and privacy implications before data is served or released.
  • Operational lineage and metadata stewardship: Ensures column-level lineage and catalog stewardship are usable for incidents and schema changes, not just documentation.
  • Access control enforcement: Validates RBAC/RLS and related audit/retention obligations so serving behavior aligns with policy and downstream risk.

Use case: Before publishing a dataset that includes PII, review whether sensitive fields have correct handling rules (masking/tokenization/access), whether column-level lineage exists for incident traceability, and whether audit and retention requirements are documented and enforceable.

Quick Start

Use this skill to review the planned serving or release of a data product for governance, privacy, access control, lineage, and retention compliance.

Frequently Asked Questions about des-persona-governance-reviewer

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

FAQPage Schema
How do I validate data governance and lineage before publishing a dataset with PII?

To validate data governance for PII datasets, review whether sensitive fields have documented handling rules like masking or tokenization, verify column-level lineage exists for incident traceability, and ensure RBAC, audit, and retention requirements are documented and enforceable before serving.

What does a data governance review check for sensitive data release readiness?

A data governance review for sensitive data release checks PII classification, evaluates masking or encryption choices, validates schema registry compatibility, and confirms access-control policies align with downstream serving risk and privacy obligations.

How do I enforce RBAC and RLS policies during a data product handoff?

To enforce RBAC and RLS policies during handoff, validate that role-based and row-level security configurations match documented access obligations, and confirm audit logging and retention rules are active so serving behavior aligns with governance policy.

When do I need column-level lineage for compliance and incident traceability?

You need column-level lineage for compliance when handling sensitive fields, as it ensures metadata stewardship is operationally usable for incident traceability and schema changes, rather than just serving as static documentation.

Does this governance review process work for schema registry compatibility checks?

Yes, the governance review process evaluates schema registry compatibility alongside metadata stewardship, ensuring catalog ownership and privacy handling are complete and operationally sound before approving a data release.