681건 · 관련도순
Two-phase memory hygiene. Phase 1: scan external Claude Code memory (~/.claude/projects/<slug>/memory/) for durable rules to migrate into the repo and entries already duplicated by repo atoms. Phase 2: audit in-repo memory/, CLAUDE.md, docs/architecture/, and docs/sections/ for dead links, duplication, drift, and bloat.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
End-of-session cleanup for coding and project work. Use when the user says "finish", "wrap up", "done for now", or any variation of ending a work session.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Spawns vehicles on a running CARLA server and destroys them — scattered across the map's spawn points on Traffic Manager autopilot, a row queued in a single lane at a fixed spacing, or a single hero/ego vehicle (optionally named for native ROS 2 publishing with --ros-name). Covers blueprint filtering, the atomic autopilot hand-off, and cleanup. Use when the user asks to "spawn vehicles/cars/traffic", "add N cars driving around", "put cars in a lane 15 m apart", "spawn the ego/hero vehicle", or "remove the vehicles".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Write, review, or audit this repository's technical documentation, including README.md, CONTRIBUTING.md, root and scoped AGENTS.md files, docs pages, and documentation drift. Use for source-backed documentation authoring, behavior verification, and cross-surface consistency. Do not use for code review, deslop diff cleanup, or whole-page rewrites, splits, or reorganizations handled by docs-refactor.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Perform a diff-scoped, behavior-neutral cleanup of AI-generated slop on the current branch before code review. Use for removing trivial comment, defensive-check, type-laundering, redundant-intermediate, compatibility-shim, or local style drift from the branch diff. Do not use for full correctness or safety review, documentation work handled by technical-documentation or docs-refactor, or repo-wide refactors.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Keep GPT-5.6 and other coding-agent work proportional to the request by locking scope, choosing the smallest sufficient implementation, matching verification to risk, and stopping when success is proven. Use for implementations, bug fixes, refactors, reviews, or maintenance where scope creep, speculative abstractions, unrelated cleanup, repeated test runs, unnecessary dependencies, or polishing beyond the request are risks.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Manage Docker containers, images, volumes, networks, and Compose stacks — lifecycle ops, debugging, cleanup, and Dockerfile optimization.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Operate and maintain OpenViking server - configure, install, start, stop, and cleanup the server. Use when need to setup or manage OpenViking service deployment.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Create standout, technically ambitious interfaces that feel extraordinary through cinematic transitions, advanced motion, heavy rendering, or other high-ambition implementation work. Use when the user wants to wow, impress, go all-out, or push a feature beyond conventional UI polish—not when simple visual confidence or routine cleanup is enough.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Add moments of joy, personality, and surprise through success states, empty states, loading moments, hover details, and celebratory polish once the fundamentals already work. Use when the user wants delight, charm, personality, or memorable micro-interactions—not when the main need is baseline cleanup or stronger visual impact.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Route code cleanup, maintainability, React diagnostics, and over-engineering review to focused review modes. Use when auditing code quality or asking for a particular review lens.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Route natural-language cleanup, refactor, migration, and candidate ranking goals through ATM before local analysis.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Intelligently organizes your files and folders across your computer by understanding context, finding duplicates, suggesting better structures, and automating cleanup tasks. Reduces cognitive load and keeps your digital workspace tidy without manual effort.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when introducing a feature flag system, choosing between release flags / experiment flags / operational flags / kill switches / permission flags, designing percentage rollouts, building kill-switch + circuit-breaker patterns, structuring evaluation contexts (user IDs, plan tier, region), or building flag-cleanup discipline. Triggers: LaunchDarkly / GrowthBook / Unleash / Flagsmith / OpenFeature, percentage ramp, sticky bucketing, kill switch wired to alerting, "we still have flags from 2 years ago", flag debt, OpenFeature provider, evaluation context, default value on provider failure. NOT for A/B test statistical analysis (separate skill), traffic-split routing at the edge, build-time bundler defines, or environment-based config.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Manage DAG execution lifecycles including start, stop, pause, resume, and cleanup. Activate on 'execution lifecycle', 'stop execution', 'abort DAG', 'graceful shutdown', 'kill process'. NOT for cost estimation, DAG building, or skill selection.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Cleanup and triage of the task ledgers FOUND_DEFECTS.md, CURRENT_ERRORS.md, .matrx/AGENT_TASKS.md, .matrx/ARMAN_TASKS.md. Use when invoked as /task-hygiene <step>, cleaning up tasks, defects, or errors, triaging an error dump, promoting defects, or bootstrapping these files.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Find and identify the CCSGameRules_ResetRound function in CS2 server binary using IDA Pro MCP. Use this skill when reverse engineering CS2 server.dll or libserver.so to locate the round-reset routine. It is the only function that references the "GMR_ResetRound\n" debug log string, and is the predecessor anchor for find-CCSGameRules_PostCleanUp (which it calls). Emits a unique IDA-style byte signature and a func YAML. Mirrors the find-CCSGameRules_ResetRound.py preprocessor (xref_strings "GMR_ResetRound\n"). Trigger: CCSGameRules_ResetRound, ResetRound, GMR_ResetRound
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
This skill should be used when the user asks to "既存プロジェクトのタスクを整理して", "技術的負債をIssue化して", "このコードベースを改善するタスクを洗い出して", "GitHub Projectに健全化タスクを登録して", "break down what needs to be fixed in this project", "surface tech debt as issues", or "create a project board for cleanup work". Diagnoses pain points and codebase health of an existing project, then registers improvement tasks as GitHub Issues and a Project Board.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
[52] EXECUTE. Three-stage refactoring workflow: (1) iterative research of refactor/modularization options, (2) plan + risk/edge-case analysis + Scope150 validation, then implement with tests after user confirmation, and (3) apply Scout105 cleanup protocol. Use when asked to refactor, modularize, or restructure code safely.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
[71] CLOSE. Quick, safe cleanup after completing a milestone. Fix objective issues only (syntax errors, dead code, poor naming). Must be <5% of main task time, <30 seconds per fix, and reversible. Use after key points, not after every small change.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
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
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Intelligently organizes your files and folders across your computer by understanding context, finding duplicates, suggesting better structures, and automating cleanup tasks. Reduces cognitive load and keeps your digital workspace tidy without manual effort.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Manage Docker containers, images, volumes, networks, and Compose stacks — lifecycle ops, debugging, cleanup, and Dockerfile optimization.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Manage track lifecycle: archive, restore, delete, rename, and cleanup
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.