메뉴
Safely GC stale agent cruft (worktrees, registrations, tmux windows, agent rows). Offers to PR un-merged work first; reports isolation clones. Usage: /ctf-clean [--dry-run]
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
| name | ctf-clean |
| description | Safely GC stale agent cruft (worktrees, registrations, tmux windows, agent rows). Offers to PR un-merged work first; reports isolation clones. Usage: /ctf-clean [--dry-run] |
| metadata | {"version":"1.0.0"} |
Reclaim stale agent cruft from the task framework. Auto-removes only worktrees
whose task is done/merged with no real uncommitted work; offers to PR un-merged
work before removing it; reports (never deletes) /isolate clones.
Safety invariant: only cruft tied to a done task is ever touched. Anything
tied to todo/in-progress/in-review is left alone — that's agent-watcher's
job, not this skill's.
--dry-run, pass it through, print the
output, and STOP — touch nothing else.
scripts/agent-clean ${ARGUMENTS}
ATTENTION lines (tab-separated: ATTENTION <task_id> <branch> <status> <why>). These are un-merged / active worktrees that were NOT
removed. For each whose why contains "un-merged" (skip ones marked "active
task"), offer three choices:
git -C <project.local_path> push -u origin task-<id>
gh pr create --repo <org/repo> --head task-<id> --title "<task title>" --body "<bullet summary>"
git -C <project.local_path> worktree remove --force <framework_root>/.workspaces/agent-<id>
<project.local_path> and <org/repo> from tasks/projects;
<framework_root> is the claude-task-framework repo root (where
scripts/agent-clean lives) — the worktree's absolute path, since it's
registered to the project repo but lives under the framework's .workspaces/.
Title + bullets follow the repo's PR conventions; if the project's org has
Jira/Discord configured, update them per the Autonomy rules.git -C <project.local_path> worktree remove --force <framework_root>/.workspaces/agent-<id> without a PR.
Worktrees marked "active task" are reported only — never offer to remove them.ISOLATION lines verbatim (tab-separated: ISOLATION <path> <size> <git summary>). These are user isolation clones — report only, never
act on them.agents rows (the sweeper only resets orphaned running rows to
cancelled).Manage App Store Connect metadata via the ASC API. Usage: /appstoreconnect
When the user wants to A/B test App Store product page elements to improve conversion rate. Also use when the user mentions "A/B test", "product page optimization", "test my screenshots", "test my icon", "conversion rate optimization", "CPP", or "custom product pages". For screenshot design, see screenshot-optimization. For metadata optimization, see metadata-optimization.
When the user wants to set up, interpret, or improve their app analytics and tracking. Also use when the user mentions "analytics", "tracking", "metrics", "KPIs", "App Store Connect analytics", "install tracking", "funnel", "attribution", or "how is my app performing". For A/B testing, see ab-test-store-listing. For retention metrics, see retention-optimization.
When the user wants to plan a launch strategy for a new app or major update. Also use when the user mentions "app launch", "launch plan", "launch checklist", "pre-launch", "launch day", or "how to launch my app". For ongoing ASO after launch, see aso-audit. For paid acquisition during launch, see ua-campaign.
When the user wants to create or update their app marketing context document. Also use when the user mentions "app context", "marketing brief", "app positioning", or when starting any ASO or app marketing project. This is the foundation skill — all other skills check for this context first.
When the user wants to get featured on the App Store or understand the editorial process. Also use when the user mentions "get featured", "App Store editorial", "App of the Day", "Today tab", "Apple featuring", or "how to get Apple to feature my app". For launch strategy, see app-launch. For ASO optimization, see aso-audit.