القائمة
Use when a RepoKernel project has dirty, untracked, stale, duplicate or unclear files and needs a non-destructive classification before cleanup, commit, archive, ignore or owner review.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Preserve continuity, sources and boundaries for Starter L1.
Use when working inside a RepoKernel repository on context-aware project structure, current state, source bootstrap, memory delta, skill lifecycle, templates, audit scripts or promotion packets.
Use when a RepoKernel project must convert an approved event and persistent intent into a bounded observe-align-distill-evaluate cycle without allowing the same process to approve its own goals, actions or evolution.
Use when a project needs a higher-leverage improvement than the visible task suggests, especially under ambiguity, repeated friction, architectural impact, conflicting sources or a transferable local insight.
Use when converting project intent, supplied documents, existing repository state and environment constraints into a custom RepoKernel seed specification and a safe generation or retrofit plan.
Use when creating a new repository or retrofitting an existing repository with RepoKernel structure: AGENTS gate, CURRENT_STATE, source bootstrap, semantic kernel, process packet, templates and audit checks.
| name | clarity-cleanup-steward |
| description | Use when a RepoKernel project has dirty, untracked, stale, duplicate or unclear files and needs a non-destructive classification before cleanup, commit, archive, ignore or owner review. |
Use this skill to reduce action noise before it becomes reentry debt.
It is a classifier and proposal skill. It is not a deletion tool, formatter, history rewriter, scheduler or automatic cleanup daemon.
CURRENT_STATE.md
sources/bootstrap/SOURCE_ATLAS_v1.0.md
docs/clarity-cleanup-cycle.md
git status / concise diff summary
existing inventory or migration reports when present
observe worktree
-> classify unclear items
-> group by owner and risk
-> propose smallest useful cleanup
-> stop before destructive action
-> validate if an owner-approved cleanup is later performed
-> write receipt only when future reentry improves
path:
observed_state: dirty | untracked | generated | stale | duplicate | unknown
owner: current-agent | operator | generated-tool | external | unknown
risk: safe | review_required | sensitive | destructive
proposed_action: keep | commit | document | archive | ignore | delete_candidate | ask_owner
evidence:
gate:
receipt:
ClarityCleanupReceipt:
surface:
checked:
dirty_items:
classifications:
proposed_actions:
blocked_actions:
validation:
next_safe_action: