kc-plugin-forge-sanitize-check

Plugin Sanitize-Check

Prepublish backstop. Greps a plugin's public files (reference/*.md, skills/**/*.md, agents/**/*.md, README.md, CLAUDE.md, docs/*.md, skill-scenarios/*.yaml) for known leak patterns. If any hit, block publish with a per-finding report so user can decide: fix, allowlist, or override.

Position in the knowledge ladder: this skill is the safety net AFTER Early-stage Dreaming. Early-stage Dreaming is the primary defense (sanitize at capture time). Sanitize-check exists only because Dreaming is human-gated and humans miss things.

When to invoke

Trigger	Action
Before making a public plugin feature PR ready	Run sanitize-check first; do not proceed if findings exist and the user does not override
Before opening a PR to a public plugin repo	Run sanitize-check on the changed files
After bulk Dreaming session	Sanity check that distilled rules don't still contain identifiers
Periodically (nightwatch)	Audit accumulated drift

Usage

/kc-plugin-forge sanitize-check <plugin-name>
/kc-plugin-forge sanitize-check <plugin-name> --strict   # treat WARN as block
/kc-plugin-forge sanitize-check --all                    # scan all kc-* plugins

Detection rules

Three rule classes, all configurable in ~/.claude/kc-plugins-config/sanitize-rules.yaml (created on first run with defaults).

Class 1 — BLOCK (literal high-signal identifiers)

Strings that should NEVER appear in public files. Match = block publish.

Default seeds (user adds their own orgs):

• DataRecce
• @recce/ (org-scoped npm package)
• reccehq.com
• bw.tw (real domain)
• pwd123 (known seed credential)
• [email protected]

User override: edit sanitize-rules.yaml block_literals: list.

Class 2 — WARN (heuristic patterns)

Regex patterns that are usually but not always identifiers. Match = warn, do not block.

Defaults (hardcoded — yaml has disable_warn: list to suppress):

• [A-Z]{2,5}-\d{2,6} (likely Linear/Jira ticket) — allow DRC-XXXX, PROJ-NNN templates
• [a-z][-a-z0-9]+/[a-z][-a-z0-9]+#\d+ (likely GitHub PR ref)
• `[0-9a-f]{7,40}` (likely short SHA in markdown code-tick)
• /Users/[^/]+/(Project|Code|Work)/ (likely local path)
• [A-Za-z0-9._%+-]+@(?!example\.com|test\.com|seed\.[a-z]+)[A-Za-z0-9.-]+\.[A-Za-z]{2,} (likely real email)
• (feature|fix|chore)/[a-z]{2,5}-\d+ (likely ticket-prefixed branch)