jh941213/codex-lattice · Archived

data-governance

Data governance workflow. Use when handling PII, privacy, retention, data classification, access control, audit logs, schema ownership, data migrations, analytics events, or compliance-sensitive changes.

Installation

$ npx skills add jh941213/codex-lattice --skill data-governance

Stronger alternatives

This repository is archived — consider an actively maintained alternative.

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from jh941213/codex-lattice · top by installs.

npx skills add jh941213/codex-lattice

Browse all from jh941213/codex-lattice

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Repository health

Stars 19
License LICENSE
Default branch main
Open issues 0
Status Archived

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 1,355 B
  • docs SUMMARY.md 226 B

History

  1. First recorded snapshot · 1 installs

SKILL.md

Data Governance

Use this skill when a change touches PII, privacy, retention, data classification, access control, audit logs, analytics events, schema ownership, or compliance-sensitive data.

Workflow

  1. Identify data classes: public, internal, confidential, secret, PII, regulated.
  2. Identify where data enters, persists, leaves, and gets logged.
  3. Confirm validation and minimization at external boundaries.
  4. Confirm retention and deletion expectations.
  5. Check access control and audit trail requirements.
  6. Check whether migrations preserve ownership and rollback expectations.
  7. Update docs/harness/DATAGOVERNANCE.md, docs/harness/DATAMODEL.md, and docs/harness/SECURITY_POLICY.md.

Red Flags

  • PII in logs, model-visible files, telemetry, screenshots, or test fixtures.
  • Broad admin access without audit.
  • Analytics events with raw user content.
  • Data retention without deletion path.
  • Schema changes without migration verification.

Required Output

Return data classes, flows, storage, retention, access controls, audit evidence, and unresolved compliance risk.