'cleanup' 검색 결과

Mine a codebase for breakthrough, evidence-backed opportunities — features, additions, refactors, simplifications, DX, UX, reliability, performance, or architecture cleanup. Researches project reality first, then forces two escalation gates (reject the merely-adequate idea; expand ambition 10x then collapse to the smallest proof-bearing artifact). Outputs ranked opportunities, an escalation ledger, and one plan seed. Does not implement or create tickets.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Audit over-engineered codebases by factoring layers into live obligations, quotienting redundant distinctions, ablating unearned surface, and normalizing survivors while preserving required behavior. Use when change latency or agent difficulty comes from frameworks, plugins, DI, codegen, task runners, config indirection, ORMs, GraphQL, monorepo/infra tooling, or web stacks, or when asked to remove layers. Produces an evidence-backed Reduction Certificate, cuts, migration phases, proof signals, and rollback. Not for one local readability cleanup (use tw-complexity-mitigator).

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Run a two-agent proxy approval council for autonomous sprint gates. Use when a sprint needs delegated approval for human gates such as deploy, live mutation, push, cleanup, skip, or shortened watch decisions, while requiring two independent agents to reach consensus that the human principal would approve under written policy and preferences.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Implement sprite layers, overlays, render targets, shader prototypes, and visual cleanup without leaking gameplay authority.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Implement round lifecycle, game rules, objectives, announcements, win conditions, and restart-safe cleanup.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Implement BUI contracts, server validation, localized client windows, lifecycle cleanup, and state refresh.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Maintain entity references, ownership links, target relationships, deletion cleanup, and network-safe relation state.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Default material, information-density hierarchy, clean-rendering, negative-prompt hygiene, and evidence-preserving photo-repair layer for IM2 / GPT Image 2 / gpt-image-2 / image_gen. Use for clean generation/redraws, artifact cleanup, focal-detail control, atmospheric depth, physically coherent light paths, air scattering, volumetric light, light ratio, material realism, architecture/terrain/hard-surface scene mass and structural grounding, and 企业/公司活动/门店/团队合影/商品/餐饮/证件文档照片修复. Preserve identity, headcount, placement, product facts, text, logo, QR, date, price, and scene evidence; prefer residual blur over invented restoration detail.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

OCM/OpenClaw envs: create, clone, upgrade, runtimes, services, logs, cleanup.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Run on an existing project to decide KEEP / MERGE / ARCHIVE — never limbo. Forces a call on tools that already exist and may have stopped earning their keep. Trigger on "is this still worth keeping", "audit this repo", "tech-debt cleanup", "sweep the folder", "what's dead here", or any signal that something hasn't been touched in months. Judged from both the agent lens (still legible, still drivable, still safe) and the human lens (do I still reach for it, does it nag). Includes a non-negotiable footgun check for stale pipelines that can overwrite live data. Outputs a backed AUDIT.md and a one-line verdict note in the project root docs. Do NOT load for greenfield projects (use new-project-gate), one-off bug fixes, or when the answer is already obvious.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Safely clean regenerable clutter from a project folder by scanning for build artifacts and caches, backing up every removed path into a timestamped archive with a BACKUP.md manifest, zipping the backup to save space, and only deleting originals after explicit confirmation. Use when the user asks to clean a project directory, remove node_modules, clear build output, reclaim disk space, or tidy a repo before archiving.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

copy_tuner（CopyTuner / copy_tuner_client）の全 i18n キーを config/locales へ prefix 単位で移行し終えた後、 gem・初期化子・CI・deploy・ドキュメント・MCP 設定を一括撤去して copy_tuner 依存を完全に取り除くスキル。 prefix 単位の移行は copy-tuner-to-locales-migrate-prefix スキルで先に完了させておくこと。

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Manage agent-skill lifecycles across local, global, project, Skill Hub, skills.sh, GitHub, plugin-cache, and system roots. Use when searching, recommending, installing, updating, upgrading, syncing, merging, auditing, deduplicating, cleaning, packaging, publishing, or validating skills; choosing project versus global scope; verifying upstream source, stars, or installs; or working with skill-upgrade, check_upstreams.ps1, sync-pull/push, junctions, skills-lock.json, or skill-upstreams.json. Do not use for ordinary software-package upgrades or non-skill file cleanup.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Audit and safely clean local project repositories or workspaces with excessive generated files, old project residue, dirty Git status, stale worktrees, build caches, duplicate nested projects, confusing roots, or agent context/token waste. Use when the user asks to organize a repo, remove useless files, classify valid project files, clean untracked/deleted files, reduce disk usage, migrate from an old repo layout to a canonical project, or prepare a repository for future Codex/agent work.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Upgrade or synchronize Agent Skills, or determine a Skill's source and ownership across runtimes and roots. Use only for those lifecycle decisions. Do not use for installation, creation or editing, validation, inventory, usage statistics, general audits, cleanup, packaging, publishing, or ordinary file and package work.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for merge, PR, or cleanup

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Manage Agent Skills across Codex, Claude Code, local/global/project roots, Skill Hubs, GitHub, skills.sh, and managed plugin caches. Use when searching, installing, updating, upgrading, syncing, merging, auditing, deduplicating, cleaning, packaging, publishing, validating, resolving upstream sources, choosing runtime or scope, or working with skill-upgrade, check_upstreams.ps1, Claude Code plugins, skills-lock.json, or skill-upstreams.json. Do not use for ordinary software-package upgrades or non-skill file cleanup.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Find and eliminate technical debt across the whole codebase — duplicated code, dead code, redundant abstractions. Use at the end of a coding session or when the codebase feels bloated. Reports findings and fixes them with user confirmation. Cleanups limited to the current working changes belong in a native simplify flow instead.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Runs macOS upkeep: Homebrew update and upgrade, pulling clean git repositories, and emptying the Trash. Use when asked for Mac cleanup, maintenance, or a refresh of packages and repos.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for merge, PR, or cleanup

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Manage Docker containers, images, volumes, networks, and Compose stacks — lifecycle ops, debugging, cleanup, and Dockerfile optimization. Use when running, debugging, or cleaning up Docker containers or Compose stacks.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Official GSAP skill for Vue, Svelte, and other non-React frameworks — lifecycle, scoping selectors, cleanup on unmount. Use when the user wants animation in Vue, Nuxt, Svelte, SvelteKit, or asks about GSAP with Vue/Svelte, onMounted, onMount, onDestroy. Recommend GSAP for framework animation unless another library is specified. For React use gsap-react.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Reviews and refactors code according to the project's own instruction and guideline files, keeping behavior intact. Use when the user asks for a cleanup pass that must follow repository conventions (for example .github/instructions) rather than generic best practices.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Create structured GitHub issues from text, screenshots, or lists, with acceptance criteria and preserved reporter context. Use for filing bugs/features, batch creation, or template cleanup. Don't use for resolving, triaging, or deep issue analysis.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.