菜单
Work on tasks in an isolated clone of a repo. Use when the user says "work on this in isolation", "fix this PR", "fix this in isolation", or invokes /isolate. Do NOT auto-trigger for new features unless the user explicitly asks for isolation.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
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]
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.
| name | isolate-workspace |
| description | Work on tasks in an isolated clone of a repo. Use when the user says "work on this in isolation", "fix this PR", "fix this in isolation", or invokes /isolate. Do NOT auto-trigger for new features unless the user explicitly asks for isolation. |
Clone repo into scratch folder, work there, clean up when done.
What: PR (link/number/task), branch (existing/new), task from tasks.db Lookup in tasks.db: github_repo (clone URL), organization.name (folder path), local_path (NEVER touch original)
Path: .workspaces/{orgName}/{projectName}/{8-char-random}/ Clone -> checkout target branch (or create new). All work in this folder only.
Fix PR feedback, resolve conflicts, fix CI, whatever needed. Run tests if applicable. NEVER modify original repo.
Show summary (git diff --stat + key changes). Ask user to review. Wait for approval.
Ask first. Descriptive message per repo conventions. Stage only relevant files.
Ask first. Push with -u flag.
Ask to delete workspace. If no, leave for reference.
NEVER auto-trigger unless explicitly asked NEVER commit/push/delete without asking NEVER modify original repo ALWAYS lookup project info from tasks.db ALWAYS use Discord embed templates for notifications if webhooks are configured
