cleanup-custody
Use when a workspace or repository surface needs a custody decision about whether to keep it live, move it to cold store or governed trash, delete it now, or route it to an owning authority.
- License 许可
- MIT
- 最近更新
- 2026-10-08
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- cleanup-custody
- license
- MIT
- metadata
- { "owner": "Harley Bartles", "status": "active", "use_when": [ "a workspace or repository surface needs classification to determine whether it should stay live, move to cold store, move to governed trash, be deleted now, or block and route to an owning authority." ], "source-id": "cleanup-custody", "source-path": "skills/cleanup-custody/SKILL.md", "do_not_use_when": [ "another more specific skill owns this task." ], "provenance-name": "Cleanup Custody first-party skill", "source-category": "first_party" }
- description
- Use when a workspace or repository surface needs a custody decision about whether to keep it live, move it to cold store or governed trash, delete it now, or route it to an owning authority.
02 资源文件 4
- 参考文档agents/openai.yaml519 B
- 参考文档CHANGELOG.md241 B
- 参考文档references/version-history.md389 B
- 脚本scripts/cleanup_scratch.py5.8 KB
03 SKILL.md 正文
Cleanup Custody
Use this skill to classify whether a workspace or repository surface should stay live, move to cold store, move to governed trash, be deleted now, or block and route to an owning authority.
This is a GPT-native cleanup, custody, and anti-bloat self-check. It does not replace repo doctrine and does not authorize deletion by itself.
If older No Shit or profanity-bearing naming appears in provenance, treat it as history only. Extract the useful anti-bloat posture without preserving profanity-bearing public naming as the active source identity.
Custody ladder
Use this ladder in order:
keep_live— current source, active doctrine, active code, required index, publication proof, protected evidence, or authoritative operating material.move_to_cold_store— retained but inactive material with lawful custody and discoverability.move_to_governed_trash— reversible deletion-staging custody with a repo-visible sentinel.delete_now— exact disposable residue with no provenance, authority, or future retrieval value.block_and_route— protected, ambiguous, actor-owned, source-law-sensitive, or authority-sensitive surfaces.
Promotion before removal
Before a surface leaves keep_live custody, migrate durable content to its owning surface: enduring architecture decisions to the repo's ADR home, operating rules to current doctrine or runbooks, and evidence to its declared proof surface. The repo's local binding names the destinations; this skill owns the step. A removal that strands durable decisions in deleted or scratch-only material is not GREEN.
Issue-goal conformance gate
When a repo and issue are in scope, cleanup review is not GREEN merely because git status is clean, residue was classified, or publication proof exists. First restate the issue goal as observable repo/workspace state, inspect the surfaces that would falsify that goal, compare worker claims to observed state, and then judge.
Require these lanes for issue-backed cleanup or self-check work:
issue_goal_as_observable_staterepo_surfaces_that_should_reflect_goalfalsification_checks_runworker_claim_vs_observed_statejudgment
If an ordinary repo tree, canary, sentinel, gitlink, or other observable marker still contradicts the issue goal, block GREEN/PASS and route the correction.
Governed-trash sentinel rule
When governed trash is involved, require a repo-local GovernedTrash/README.md sentinel posture or the repository's established equivalent. Any governed-trash add, remove, or clear action must refresh and publish the sentinel before GREEN.
Do not treat the sentinel as deletion authority. It is custody inventory and publication proof for trash handling.
Trigger examples
Use this posture for:
- skill sprawl or duplicate operational entrypoints;
- stale helper wrappers or fake compatibility layers;
- temp, build, cache, scratch, and generated residue;
- obsolete governance duplicates;
- wrong-home cross-project artifacts;
- issue/process clutter created only to prove cleanup;
- governed-trash or cold-store custody decisions.
Protected surfaces
Block and route instead of cleaning when a surface may be:
- archive evidence or provenance;
- canon/world truth or ambiguity-bearing material;
- manuscript prose, authorial notes, or draft candidates;
- live data, machine truth, backups, receipts, or publication proof;
- source-law, actor/domain authority, current operational doctrine, or project-protected material.
Anti-bloat rule
Prefer the smallest final lawful surface, not the smallest immediate edit. Do not preserve wrappers, compatibility layers, or duplicate doctrine just because they already exist. But do not collapse actor/domain separation, provenance, ambiguity, or local binding pages merely to reduce file count.
Return checks
When applying this posture, report:
- custody decision for each path or surface;
- protected surfaces checked;
- residue created, discovered, and cleaned before GREEN;
- whether governed-trash sentinel inspection/update is required;
- retained exceptions and their removal condition;
- false-green risks still open;
- for issue-backed work, the issue goal as observable state, falsification checks run, worker claim versus observed state, and judgment.
False-green risks
- using anti-bloat as a deletion-first hammer;
- deleting evidence, canon, prose, receipts, reports, or proof surfaces;
- treating fewer files as automatically better;
- moving material to governed trash without refreshing the sentinel;
- calling cleanup GREEN while residue or stale indexes remain;
- calling issue-backed cleanup GREEN while observable repo/workspace state still contradicts the issue goal;
- treating clean status, remote-head equality, changed-file lists, or validation claims as substitutes for issue-goal conformance.
04 同仓库更多 Skills
writing
Use when drafting, revising, or reviewing prose for human readers and clarity, an authorised voice, or reader-fatigue concerns may interact.
writing-with-clarity
Use when drafting, revising, or reviewing prose intended for human readers, including documentation, README files, reports, explanations, UI copy, errors, comments, commit messages, and pull request text.
writing-style
Use when revising or reviewing human-facing prose against an authorised voice card or a contextual reader-fatigue profile.
skill
暂无简介
writing-skills
Use when creating new skills, editing existing skills, or verifying skills work before deployment.
writing-roadmaps
Use when a goal is too large for one writing-plans plan and requires a sequenced roadmap of consecutive plans.