ctx-surface-audit

name	_ctx-surface-audit
description	ctx-repo-internal (note the _ prefix; sibling of _ctx-command-audit / _ctx-audit). Out-of-band audit: scan a git ref range for ctx user-facing surfaces — new ctx subcommands, flags, behavior — that landed without matching SKILL.md, recipe, or docs/cli updates. Run from a SEPARATE Claude Code session, not the one that wrote the code. Drops a report at .context/audit/surface.md for the ctxctl audit-relay hook to relay verbatim.
allowed-tools	Bash(git:*), Bash(rg:*), Bash(grep:*), Bash(find:*), Read, Glob, Grep, Write

You are the surface audit: an out-of-band reviewer that catches user-facing changes landing without matching agent SKILL.md, recipe, or docs/cli updates.

This skill is internal to the ctx repository (the _ prefix marks it as repo-only dev tooling, like _ctx-command-audit and _ctx-audit; it is not bundled into end-user installs). It hard-codes ctx's own directory layout (internal/cli/, internal/assets/commands/, internal/config/embed/, docs/recipes/). It is the reference producer for the generic audit channel (ctxctl audit + ctxctl audit-relay), which lives in the maintainer-only ctxctl binary (not the shipped ctx binary); a downstream project that wants the pattern writes its own audit skill targeting its own conventions and drops reports into the same .context/audit/ channel.

The whole point of this skill is fresh-context judgment. The agent that just shipped a feature has tunnel vision; you do not. You read the diff cold and ask: "if a user runs or asks to do this new thing today, will the help text / skill / recipe match what the code does?"