agentleFS
SafetyMPSafetyMP/HR-ERP/.github/copilot-instructions.md

HR-ERP

Copilot instructions1 starsChanged 6 months agoApache-2.0View on GitHub

This repository is an HR scaffold for testing agent governance on a multi-tenant SaaS fixture. Do not move the community contract out of AGENTS.md. Factory/site overlay lives in docs/factory-overlay.md. Do not claim green from prose. Community contract: AGENTS.md. Pivot: docs/DESIGN-PIVOT.md. High-risk fixture DDL: .github/skills/hr-data-custody/SKILL.md. Follow path-specific files in .github/instructions/. Copilot code review loads .github/skills/code-review/.

The file

We split this copilot-instructions.md into the rules it gives an agent

7 rules. About 0 are common, 5 are distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈5

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Do not claim green from prose.

    line 12
  2. Distinctive:

    Never treat this tree as a certified payroll vendor or production HRIS.

    line 16
  3. Distinctive:

    Never commit real employee, tax, or payroll PII.

    line 17
  4. Distinctive:

    Never duplicate Cedar, receipt ledgers, or sandbox runtimes here.

    line 18
  5. Distinctive:

    Never self-approve, invent a gate PASS, or edit corporate approval state.

    line 19
  6. Very specific:

    Never set NEXT_PUBLIC_ALLOW_DEMO_DEV_SIGNIN on Vercel Production.

    line 20
  7. Very specific:

    Follow path-specific files in .github/instructions/.

    line 28

≈ “Common” is an estimate: at least 1 in 5 of the 3,827 Copilot instructions 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
copilot-instructions.md

Copilot / community agents

This repository is an HR scaffold for testing agent governance on a multi-tenant SaaS fixture. Do not move the community contract out of AGENTS.md. Factory/site overlay lives in docs/factory-overlay.md.

Verify

  • ./scripts/harness/verify.sh — Definition of Done
  • ./scripts/verify.sh — optional human wrapper
  • npm run governance:lint / governance:ci — tier + merge gates
  • ./scripts/adversarial.sh — authorized probes only

Do not claim green from prose.

Never

  • Never treat this tree as a certified payroll vendor or production HRIS.
  • Never commit real employee, tax, or payroll PII. Synthetic fixtures only.
  • Never duplicate Cedar, receipt ledgers, or sandbox runtimes here. Pair FidusGate for runtime receipts.
  • Never self-approve, invent a gate PASS, or edit corporate approval state.
  • Never set NEXT_PUBLIC_ALLOW_DEMO_DEV_SIGNIN on Vercel Production.

Community contract: AGENTS.md.
Pivot: docs/DESIGN-PIVOT.md.
High-risk fixture DDL: .github/skills/hr-data-custody/SKILL.md.

Coding standards

Follow path-specific files in .github/instructions/. Copilot code review loads .github/skills/code-review/.

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.