Release Check Hygiene

Do Not Use When

• Need git branch, tag, or remote state only; use release-check-repo instead.
• Need rollout risk or rollback judgement; use release-verdict instead.
• Need to rewrite docs directly; use doc-write, doc-curate, or doc-publish-readme instead.

Required Inputs

• HYGIENE_SCOPE (diff|repo; required; allowed: diff|repo): Release hygiene scope under inspection.
• REQUIRED_DOCS (list; optional; shape: {PATH, WHY_REQUIRED}): Docs that must be updated or present before release and are expected to remain public after the release.
• SURFACE_CONTRACTS (list; optional; shape: {CONTRACT, SOURCE}): Public-surface contracts such as skill-metadata/docs parity or required path ownership.
• LEGACY_PATTERNS (list; optional; shape: {PATTERN, WHY_BLOCKING}): Names, files, or patterns that must not survive the release, including delivery-only implementation docs.

Input Contract Notes

• REQUIRED_DOCS should list only release-blocking docs, not every nice-to-have document in the repository.
• SURFACE_CONTRACTS should be observable contracts, such as skill-metadata/docs parity or root README ownership, not abstract taste rules.
• LEGACY_PATTERNS is for concrete legacy removal checks, not for broad cleanup brainstorming.
• Delivery-only planning docs such as plans/IMPLEMENTATION-PLAN.md and plans/TASKS.md belong in LEGACY_PATTERNS so the hygiene gate can require their deletion before release.
• Prefer exact skill names, file paths, or anchored patterns over broad words such as 'release' that would match unrelated content.

Structured Outputs

• HYGIENE_FINDINGS (list; required; shape: {ISSUE, LOCATION, EVIDENCE, BLOCKS_RELEASE}): Concrete hygiene problems such as stale docs, leftover legacy surface, or unsynced public references.
• DOC_GATE_STATUS (pass|blocked|inconclusive; required; allowed: pass|blocked|inconclusive): Whether required release docs are ready.
• SURFACE_SYNC_STATUS (pass|blocked|inconclusive; required; allowed: pass|blocked|inconclusive): Whether skill metadata, skill docs, and user-facing docs stay in sync.
• REQUIRED_CLEANUPS (list; required; shape: {ACTION, WHY}): Bounded cleanup actions required before release.

Output Contract Notes

• If required release docs are missing or stale, DOC_GATE_STATUS should be blocked instead of buried in a note.
• SURFACE_SYNC_STATUS should reflect observable mismatches only, such as skill-metadata/doc drift or surviving legacy names.
• REQUIRED_CLEANUPS should stay bounded and release-relevant rather than turning into a generic improvement backlog.
• HYGIENE_FINDINGS and REQUIRED_CLEANUPS may both be empty when docs and public surface are already clean.

Primary Lens

• primary_lens: release-gatekeeper
• why: Release hygiene should be judged as delivery safety, not as optional cleanup, because stale docs and legacy public surface create real rollout risk.

Artifacts

• artifacts_in: none
• artifacts_out: release-hygiene-report.v1

Neutrality Rules

• Do not invent hygiene blockers when docs and public surface evidence is clean.
• Treat missing release docs or stale public references as release risk, not as optional polish.
• Keep release-blocking hygiene issues separate from non-blocking cleanup ideas.

Response Format

Think and operate in English, but deliver the final response in Korean. 쉽고 간결한 한국어로 답하라. 전문 용어 금지. 핵심만 간단하게.

Show gate status up front:

• Doc gate: 통과 / 중단 / 미확인
• Surface sync: 통과 / 중단 / 미확인

List hygiene findings that block release:

• [issue] — file or path — blocks release: yes/no

Show required cleanup actions: [action] — [why]

If clean: "Docs and public surface are ready — no required cleanup found."

Execution Constraints

• Do not edit files from this skill; it is a check-only release gate.
• If docs upgrade is required and not evidenced, block release instead of assuming the docs will catch up later.
• Treat delivery-only implementation docs as stale release surface unless they were explicitly promoted into maintained public docs.
• Keep findings traceable to concrete files, paths, or public-surface contracts.