agentleFS
SafetyMPSafetyMP/HR-ERP/.github/skills/hr-data-custody/SKILL.md

hr-data-custody

Skill1 starsChanged 6 months agoApache-2.0View on GitHub

Change HR-ERP Prisma/SQL and RLS-safe migrations. Use for DDL, backfills, or db:verify — this is a high-risk fixture domain, not a payroll product.

The file

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 2 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Read-only schema questions with no migration intent

    line 26
  2. Very specific:

    Run npm run db:verify after migrate deploy in CI/local evidence.

    line 34
  3. Distinctive:

    Never migrate real employee or tax PII

    line 45

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

HR data custody

Community copy of the in-IDE skill at .cursor/skills/hr-data-custody/SKILL.md. Payroll/ESS schema is a fixture domain for agent-governance blast radius — not a payroll product.

Collaboration plane: Specialized skill — invoke only after phase 6 / revalidationConfirmed. Record DDL tradeoffs in collaboration-plan.md.

Use this skill when

  • Editing prisma/schema.prisma, prisma/migrations/**, services/*/db/migrations/**
  • Backfills, RLS migrations, or scripts/db-verify-migration.ts
  • Dockerfile, GHCR publish, SBOM/Cosign (ADR 0003)

Do not use this skill when

  • Read-only schema questions with no migration intent
  • Application code with no DDL/infra change
  • Trying to “complete” an HRIS against ERPNext — see docs/DESIGN-PIVOT.md

Instructions

  1. Read references/migration-runbook.md.
  2. Apply expand → migrate → contract; CONCURRENTLY discipline for indexes.
  3. Run npm run db:verify after migrate deploy in CI/local evidence.
  4. Co-load @hr-domain-boundaries when bounded-context SQL changes.

Resources

  • references/migration-runbook.md
  • specs/alignment/decisions/0003-container-supply-chain.md

Limitations

  • Zero-downtime posture required for production-like fixture paths
  • Never migrate real employee or tax PII

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.