disclosure-check ยท diff

git:20261106.064d774 to git:20261106.a8c8716

9 added, 2 removed. Audit A to A.

What this update changes in the checks

No check changed: every fixed check gives the same answer before and after this update.

A tripped check is a label, not a verdict: read the matched text and the lines below. This week's updates that newly trip a check.

---
name: disclosure-check
description: Pre-screen analysis outputs (tables, figures, logs) built on restricted or confidential data for statistical-disclosure-limitation problems before any release. Scans for small cell counts, complementary-suppression gaps, dominance (p-percent / (n,k)), re-identifiable exact counts, PII leakage, and unrounded sensitive statistics; classifies each finding CRITICAL / WARNING / OK and gates on any CRITICAL. Use before depositing or sharing restricted-data results, or when the user says "disclosure check", "SDL scan", "is this output safe to release", "check for small cells", "disclosure avoidance", "pre-screen for the RDC", or "can I export this from the enclave".
---
<!-- Generated by scripts/sync-agent-skills.py from .claude/skills/disclosure-check/SKILL.md. Do not edit: change the source and re-run the script. -->
# disclosure-check
This skill's instructions live in [`.claude/skills/disclosure-check/SKILL.md`](../../../.claude/skills/disclosure-check/SKILL.md).
Read that file now and follow it, with the files it points to. Read [`AGENTS.md`](../../../AGENTS.md)
first if you have not already.
It was written for Claude Code. Running it from Codex, Antigravity or another agent:
- **Arguments.** Where it says `$ARGUMENTS`, use what the user asked for.
- **Claude Code agents.** Where a step hands work to an agent in `.claude/agents/` (through the
- `Agent` or `Task` tool), read that agent's file and do the step yourself after the main work.
- Tell the user the step was not an independent review: the same agent did both.
+ `Agent` or `Task` tool), do that step where it appears in the procedure: never later, and never
+ skip it. A step that gates what follows still gates it (`/commit` runs its verifier before it
+ commits). Read the agent's file for what the step checks.
+ - **Fresh context.** If the step needs a context that has not seen your work, for example a claim
+ verifier that must never see the draft, run it in a separate session or worker that has not
+ seen the draft, if your tool can start one, and give it only what the step says to pass. If it
+ cannot, do the step yourself, mark every result it produced *not independently verified*, and
+ tell the user to repeat that check in Claude Code (`/verify-claims` for citations) before
+ relying on it.
- **Claude Code settings.** `allowed-tools`, `model`, `effort`, `argument-hint` and
`disable-model-invocation` in the source's frontmatter configure Claude Code. Ignore them.
- **Guards.** Claude Code's guard hooks do not run for you. Follow the rules in `AGENTS.md`
yourself; the git pre-commit gate and CI still apply to your commits.