Use when release readiness depends on legacy removal, document freshness, and public-surface sync. Do not use for branch mutation or rollout-risk judgement.
Verify release hygiene gates such as required docs, stale or legacy surface removal, and skill-metadata-to-doc sync before release judgement or publication.
[stages: preflight>detect>analyze>review>handoff>audit |
scope: diff|repo |
policy: evidence,safety-gates,quality-gates{docs,release,surface-sync},deterministic-output |
lens: release-gatekeeper |
output: md(contract=v1)]
This skill uses release-gatekeeper because it keeps the work aligned with: Treat release as a sequence of explicit gates and judge only the gate in scope with concrete evidence.
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.plans/IMPLEMENTATION-PLAN.md and plans/TASKS.md belong in LEGACY_PATTERNS so the hygiene gate can require their deletion before release.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.primary_lens: release-gatekeeperwhy: Release hygiene should be judged as delivery safety, not as optional cleanup, because stale docs and legacy public surface create real rollout risk.artifacts_in: noneartifacts_out: release-hygiene-report.v1Think and operate in English, but deliver the final response in Korean. 쉽고 간결한 한국어로 답하라. 전문 용어 금지. 핵심만 간단하게.
Show gate status up front:
List hygiene findings that block release:
Show required cleanup actions: [action] — [why]
If clean: "Docs and public surface are ready — no required cleanup found."