'cleanup' 검색 결과

Batch-Dateioperationen (Löschen, Verschieben, Kopieren, Auflisten) mit Glob-Mustern. CLI-Werkzeug für effiziente Dateisystem-Operationen. Ohne Abhängigkeiten.

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

Einmaliger Tasksolver+Writer+Maintainer-Durchlauf fuer den Projektordner, in dem die Session gerade sowieso gearbeitet hat (inkl. Unterordner) — kein systemweiter Sweep. Loest offene triviale/autonome Register-Punkte, aktualisiert Dokumentation auf den gemessenen Ist-Stand (im Projekt UND in der Root der Pipeline, in der das Projekt liegt) und raeumt Strays/Temp- Dateien nach dem Papierkorb-Prinzip weg. Nutze diesen Skill bei /tidy-up, "raeum das Projekt auf", "mach hier sauber bevor wir weitermachen", am Ende einer Arbeitssitzung an einem Projekt, oder als faellige autonome Aufgabe innerhalb von /work-autonomous + /goal.

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

Design and review Action Scheduler jobs in WordPress plugins using Action Scheduler 3.9.x public APIs - async, single, recurring, and cron-expression actions; action_scheduler_init load timing; hook/args/group naming; unique and priority parameters; idempotent callbacks; chunked workloads; activation/deactivation cleanup; WooCommerce-bundled or standalone dependency usage; admin and WP-CLI debugging; queue runner limits; and safe operational troubleshooting. Use when a plugin schedules background jobs with as_enqueue_async_action, as_schedule_single_action, as_schedule_recurring_action, as_schedule_cron_action, as_get_scheduled_actions, or integrates with WooCommerce background queues.

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

Designs and reviews scheduled/background work in WordPress plugins: wp_schedule_event, wp_schedule_single_event, cron_schedules, wp_next_scheduled guards, activation scheduling, deactivation cleanup, WP-Cron pseudo-cron timing, DISABLE_WP_CRON/system cron, multisite per-blog cron, idempotent callbacks, chunking, and Action Scheduler graduation. Use when adding scheduled jobs, debugging late/duplicate cron events, or deciding between WP cron and Action Scheduler.

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

Designs and reviews the three lifecycle events of a WordPress plugin — activation (one-shot setup, dbDelta, add_option seeding, cron schedule, cap seeding), deactivation (reversible cleanup, cron clear via wp_unschedule_hook, never delete user data), and uninstall.php (standalone file, WP_UNINSTALL_PLUGIN guard, no autoloader, full data removal). Multisite-aware patterns using the $network_wide / $network_deactivating callback args, plus the recommendation against register_uninstall_hook in favor of uninstall.php. Use when scaffolding a plugin or debugging ghost cron events / orphan options. Triggers on register_activation_hook, register_deactivation_hook, uninstall.php, WP_UNINSTALL_PLUGIN, dbDelta, wp_unschedule_hook, switch_to_blog.

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

You are a technical debt expert specializing in identifying, quantifying, and prioritizing technical debt in software projects. Analyze the codebase to uncover debt, assess its impact, and create acti

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

Detects Vitest test-isolation hazards: unrestored vi.spyOn/vi.mock without afterEach cleanup or restoreMocks config, un-awaited resolves/rejects assertions, and shared mutable module state across tests.

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

Background processing and heavy computations using Dart Isolates with Isolate.run(), compute() function, and platform channels. Use this skill when performing CPU-intensive operations without blocking UI (image processing, data parsing, encryption), implementing background tasks that prevent jank or frame drops, handling large file operations (JSON parsing, database migrations), running parallel computations, fixing UI freezes caused by main thread blocking, using compute() for one-off background work, creating long-lived Isolates with ReceivePort/SendPort, implementing multi-threaded algorithms, debugging isolate communication issues, or preventing memory leaks from unclosed ReceivePorts. Covers isolate spawn, message passing, ReceivePort cleanup (CRITICAL for leak prevention), SendPort communication patterns, error handling, serialization rules, and performance optimization for compute-heavy operations.

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

Provider (v6.x) state management for Flutter using ChangeNotifier and InheritedWidget with MVVM architecture pattern. Use this skill when implementing Provider-based state management, using Consumer/Consumer2 widgets for targeted rebuilds, accessing state with context.read/context.watch/context.select, setting up ChangeNotifierProvider or StateNotifierProvider, configuring MultiProvider for multiple providers, implementing ProxyProvider for dependent state, using Selector for optimized rebuilds, migrating from StatefulWidget to reactive state, maintaining legacy Provider codebases, debugging provider not found errors, preventing memory leaks with proper ChangeNotifier disposal, fixing context access issues in initState, or resolving .value constructor anti-patterns. Essential for apps with shared state across widgets (shopping carts, authentication, global settings, form state, theme management), when teaching state management fundamentals, or when debugging memory leaks and resource cleanup in Provider-based applications.

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

Three.js architecture: production-level scene/camera/renderer resize cleanup. Use when implementing, reviewing or testing three.js architecture for React, Vite, Next.js or Perfect_AI projects.

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

Responsive scope: production-level createScope lifecycle, media query gating, cleanup. Use when implementing, reviewing or testing responsive scope for React, Vite, Next.js or Perfect_AI projects.

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

Install, verify, and operate mdoctor on macOS and Debian/Arch-based Linux. Use when users ask to set up mdoctor, install dependencies, test branch builds on the current machine, run first health checks, troubleshoot install/runtime issues, or perform safe cleanup/fix workflows with mdoctor commands.

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

You are a dependency security expert specializing in vulnerability scanning, license compliance, and supply chain security. Analyze project dependencies for known vulnerabilities, licensing issues,...

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

You are a technical debt expert specializing in identifying, quantifying, and prioritizing technical debt in software projects. Analyze the codebase to uncover debt, assess its impact, and create acti

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

You are a code refactoring expert specializing in clean code principles, SOLID design patterns, and modern software engineering best practices. Analyze and refactor the provided code to improve its...

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

Use when running the dev Grafana stack and/or the Playwright e2e suite against a *packaged* plugin zip (a release/RC artifact like `hydrolix-hydrolix-datasource-<ver>.zip`) rather than the working-tree `dist/`. Unpacks the package into a timestamped `dist_<timestamp>/dist` sandbox alongside copies of the compose artifacts, so the run is reproducible and the folder stays available to experiment with afterwards. Delegates stack bring-up to `stack-run` (frozen mode: read-only mount + `DEV=false` so the mage-watcher can't rebuild the packaged Go binary), verifies signature/version, runs the suite, and treats cleanup as optional — the sandbox is deleted only with the user's approval. Apply whenever the task is "test this plugin package / zip" or "run e2e against the built artifact".

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

Use this skill when handling app foreground/background, Ionic view events, Vue mount/unmount, or listener registration and cleanup.

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

Reads invocation logs from eval_tracker and recommends which of the 50+ skills to prune or consolidate. Run monthly to keep the skill surface tight. Triggers: "audit skills", "prune skills", "which skills do I never use", "skill cleanup".

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

Multi-tiered memory management (HOT/WARM/COLD) for context compaction. Invoke ONLY for explicit compaction events: post-`/compact` cleanup, MEMORY.md tier promotion, archive batch, or "trim my context". NOT for general recall (use deep-recall) or routine memory writes (use storage-router). Triggers: "compact memory", "promote to durable", "archive old context", "tier this".

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

Use when working with Gcp Artifact Registry — google Artifact Registry repository management, vulnerability scanning analysis, cleanup policy configuration, and artifact lifecycle management via gcloud CLI.

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

Use after generating code, after accepting AI suggestions, or when reviewing AI-written modules. Also use when code works but feels brittle, when error handling seems thin, when orphaned resources or missing cleanup are suspected, or when the agent claims done but hidden debt may exist. Catches the specific failure patterns AI agents produce that humans would not.

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

Complete feature development with structured options for merge, PR, or cleanup

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

Audit and rewrite content to remove AI writing patterns ("AI-isms"). Supports detect-only audits, edit-in-place file cleanup, voice and context profiles, and an iterate-to-convergence pass.

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

Review code for readability, then simplify it to be easy to follow and understand. Use this skill when the user wants to simplify code, improve readability, clean up for handoff, make code skimmable, reduce complexity, refactor for clarity, strip boilerplate, prepare code for future maintainers, or make a codebase easier to pick up. Trigger liberally — any request touching readability, simplification, cleanup, or "make this easier to understand" should use this skill. Also trigger when the user says things like "review this", "clean this up", "tidy this", "make this simpler", "reduce complexity", "flatten this", "strip the noise", or "I want to understand this code quickly next time I open it".

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