Results for “cleanup”

Find and identify the CCSGameRules_PostCleanUp function in CS2 server binary using IDA Pro MCP. Use this skill when reverse engineering CS2 server.dll or libserver.so to locate the post-round entity-cleanup routine. It is non-virtual and has no unique string of its own, so it is found via the CCSGameRules_ResetRound predecessor: PostCleanUp is the entity-cleanup call ResetRound makes. Emits a unique IDA-style byte signature and a func YAML. Mirrors the find-CCSGameRules_PostCleanUp.py preprocessor (LLM_DECOMPILE CCSGameRules_ResetRound). Trigger: CCSGameRules_PostCleanUp, PostCleanUp, CGameRules::PostCleanUp

The English summary is being prepared. Showing the original description.

Identify unused AWS resources, estimate potential savings, and prepare cleanup scripts with preview steps. Covers storage retention policies and scheduled cleanup so teams can review dependencies before removing resources and track the resulting savings.

• Inventory unused resources and estimate savings
• Prepare cleanup scripts for EBS volumes and Elastic IPs
• Review S3 versions and storage retention rules

Analyze disk usage on macOS or Windows, identify large folders, and classify cleanup candidates by the care they need. Generate an interactive HTML report with estimated space savings, cleanup guidance, and optional browser controls for deleting selected files.

• Finding large folders when disk space runs low
• Reviewing caches and downloads before cleanup
• Identifying which app owns an unfamiliar large folder

Maintain data retention in ClawHub's Convex tables by classifying each table, defining expiration fields, and bounding cleanup jobs. Guide changes to temporary data and expired authentication records, with focused tests and runtime verification.

• Classify retention policies for new tables
• Add expiration fields and indexed cleanup
• Update scheduled jobs with bounded deletion batches

AWS Cost Cleanup workflow skill. Use this skill when the user needs Automated cleanup of unused AWS resources to reduce costs and the operator should preserve the upstream workflow, copied support files, and provenance before merging or handing off.

The English summary is being prepared. Showing the original description.

AWS Cost Cleanup workflow skill. Use this skill when the user needs Automated cleanup of unused AWS resources to reduce costs and the operator should preserve the upstream workflow, copied support files, and provenance before merging or handing off.

The English summary is being prepared. Showing the original description.

Review recent code changes from four angles: reuse, quality, efficiency, and whether fixes address underlying mechanisms. Combine findings, apply suitable cleanup with tests, and leave changes that could affect behavior for human review.

• Cleaning up recent code changes
• Finding duplicated logic and reusable helpers
• Reviewing efficiency in the last commit

Structure Python code to release files and database connections reliably, including when errors occur. Covers context managers, which handle setup and cleanup, asynchronous resources, nested cleanup, and streaming responses that retain accumulated state.

• Releasing database connections when errors occur
• Cleaning up files and temporary files
• Creating asynchronous context managers

Audit C/C++ and Rust code for secrets left in memory. It checks missing or incomplete wipes, examines compiler output for removed cleanup operations, and produces reports with evidence and suggested fixes.

• Auditing cryptographic key cleanup
• Checking password and token memory wipes
• Investigating cleanup removed by compiler optimization

Identify stale and empty Claude Code sessions in the Agent Monitor and explain the cleanup endpoint (POST /api/settings/cleanup), always showing the exact list of what WOULD be removed before anything is deleted. Cleanup permanently deletes data, so this skill previews first and requires explicit user confirmation. Use when tidying the monitoring database.

The English summary is being prepared. Showing the original description.

Systematic code cleanup and refactoring agent that identifies and fixes code quality issues without changing functionality. Focuses on: - Dead code removal - Import organization - Type improvements - Consistent patterns - File organization Use when "User asks to "clean up" code, User mentions "dead code" or "unused", User wants to "organize imports", User asks about "code quality", User wants to "refactor" without changing behavior, Code review identifies cleanup items, After major feature completion, cleanup, refactoring, code-quality, maintenance, organization" mentioned.

The English summary is being prepared. Showing the original description.

Use when executing admin-level cleanup in a Salesforce org: deleting unused fields, removing inactive Flow versions, deactivating legacy automation, running Salesforce Optimizer or Org Check, and performing destructive metadata deploys. Triggers: 'clean up unused fields', 'delete inactive flows', 'run Optimizer', 'org has too many custom fields', 'remove old workflow rules', 'Flow version limit'. NOT for assessing or reporting on technical debt (use architect/technical-debt-assessment). NOT for code-level refactoring or Apex cleanup (use apex/ skills).

The English summary is being prepared. Showing the original description.

Clean up the local workspace after a dev branch has been merged into main. Verifies the current dev branch is fully merged into origin/main, then switches to main, pulls the latest, deletes the local dev branch, and deletes the remote dev branch if it still exists. STOPS and warns the user if the current branch is not yet merged. Triggers: cleanup workspace, cleanup branch, delete merged branch, finish dev branch, post-merge cleanup

The English summary is being prepared. Showing the original description.

Undo a haircut trim. Puts back the skills, commands, subagents, MCP servers, hooks, plugins and files that haircut parked into a dated bag, using the receipt it wrote at the time. Use this skill whenever the user says undo the cleanup, undo the haircut, put my config back, restore what was trimmed, I need that MCP server again, that skill is gone and I want it back, roll the trim back, what is in the bag, or which files were moved. Use it also when something stopped working right after a config cleanup and they suspect the cleanup caused it, and whenever they ask how to reverse a config cleanup they regret.

The English summary is being prepared. Showing the original description.

Build GSAP animations in React or Next.js with guidance on useGSAP, element references, and component boundaries. It covers cleanup when components update or disappear, plus keeping animation code out of server rendering.

• Adding GSAP animations to React components
• Cleaning up animations when components are removed
• Keeping animations within the intended component

Find unused TypeScript code, verify references with a language server, and assign removals to parallel agents. Group changes by file, create separate commits, and check types, tests, and the build after cleanup.

• Remove unused imports, functions, and types
• Clean up a specific file or directory
• Check whether unreferenced files can be removed

Integrate GSAP animations into React and Next.js components using useGSAP, element references, and scoped selectors. The skill guides dependency updates, event callbacks, and cleanup when components unmount, while keeping animation code out of server rendering.

• Adding GSAP animations to React components
• Restricting animations to elements within one component
• Cleaning up animations when components unmount

Simplify code once its behavior is understood. Confirm the existing behavior through tests or reproduction, reduce unnecessary complexity in small, reviewable steps, and keep verification passing while preserving behavior and necessary safety checks.

• Making code easier to read without changing behavior
• Reducing complexity after confirming existing behavior
• Reviewing cleanup changes in small steps

Stop an active OMX workflow after identifying its session and related modes. Perform the required cleanup, preserve resumable state where specified, and report the outcome, including any cleanup failures or reasons for refusing to proceed.

• Stop an active OMX workflow
• Cancel Autopilot while preserving resumable state
• Shut down a selected Team runtime

Connect Solid Table v9 tables to Devtools and troubleshoot missing inspection targets. This skill guides table registration, unique keys, conditional activation, automatic cleanup, and the distinction between development exports and explicit production imports.

• Connect a Solid Table instance to Devtools
• Investigate tables missing from Devtools
• Check registration keys and lifecycle cleanup

Connect TanStack Table instances to developer tools for inspecting options, state, features, columns, rows, and row models. Diagnose missing connections, assign unique table keys, and manage registration replacement and cleanup.

• Inspect table options, state, columns, and rows
• Diagnose tables missing from developer tools
• Assign distinct keys to multiple tables

Scan a codebase for technical debt—issues that make future maintenance harder—and prioritize fixes using business impact and effort. Generate a ranked backlog, sprint allocations, and trend reports to assess cleanup work over time.

• Assess technical debt across a codebase
• Prioritize refactoring for the next sprint
• Compare debt levels before and after cleanup

Clean up GitHub issue and pull request titles by removing bracketed NemoClaw tags. It previews proposed changes, applies them after approval, and checks for remaining matches while preserving other tags and plain-text mentions.

• Removing bracketed NemoClaw tags from titles in bulk
• Previewing title changes before applying them
• Limiting cleanup to open or closed items

Release all active PUA agent and loop state from Codex using the teardown protocol, which governs cleanup. This alias corresponds to `/pua:teardown-all` in Claude Code and explains destructive cleanup before deleting files.

• Releasing all active PUA agent state
• Releasing active loop state
• Reviewing destructive cleanup before file deletion