Results for “unused”

Identify and analyze unused or redundant code including unused functions/methods, unused variables/imports, unreachable code, and redundant conditions. Use when cleaning up codebases, improving maintainability, reducing technical debt, or conducting code quality audits. Analyzes Python code using AST analysis and produces markdown reports listing dead code locations with line numbers, severity ratings, and recommendations. Triggers when users ask to find dead code, remove unused code, identify unused imports, find unreachable code, or clean up redundant logic.

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

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

Analyze Axiom data ingestion and query usage to identify unused columns and field values. Build cost dashboards and spike monitors, then summarize recommendations for dropping or sampling data with estimated savings.

• Find unused data that contributes to Axiom costs
• Track ingestion trends and projected spending
• Set up alerts for ingestion and query cost spikes

backlog（atoms/pipeline/outputs）と skill ヘルス（usage/duration/unused）を統合分析し 1 レポートで提示する。kawai 氏型 analytics ループの起点。「次に何やる？」「atom 整理」「放置案件」「stale」「振り返り」「retro」「skill 使用統計」「unused skill」「atom-suggest」で発動。

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

Audit a Claude Code setup for installation problems, broken settings, unused extensions, and duplicated instructions. It reviews local usage evidence, recommends cleanup, and applies approved fixes, with separate confirmation for permission changes.

• Diagnose installation and configuration problems
• Review unused skills, MCP servers, and plugins
• Trim duplicated or unnecessary CLAUDE.md guidance

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

Audits recurring SaaS charges against a subscription register using Plaid data. Reports duplicate tools, unused seats, price increases, upcoming renewals, and unlisted charges in a Slack digest, with suggested actions and a ledger tracking previous findings.

• Review weekly SaaS spending against the subscription register
• Find overlapping tools and potentially unused seats
• Check price increases and approaching renewals

Removes unnecessary code from a repository while preserving exactly the behavior exercised by a given test suite. Use this skill when you need to debloat, slim down, or remove unused code from a codebase based on test coverage. The skill analyzes which code elements (files, classes, functions, methods, branches, imports) are exercised by tests, identifies unreachable or unused code, and safely removes it while ensuring all tests continue to pass. Triggers when users ask to remove unused code, debloat based on tests, eliminate dead code guided by test coverage, or slim down a repository to only test-required functionality.

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

Use when the user says 'clean up my wordpress', 'what is bloating my wordpress', 'find orphaned shortcodes', or 'scan for unused plugins'. Audits orphaned shortcodes from deleted plugins, unused plugins, database bloat, unused media, and leftover data from inactive builders.

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

Use when safely removing dead frontend code, unused exports, stale components, obsolete routes, unused dependencies, or cleanup targets found by tools such as knip, depcheck, ts-prune, TypeScript, ESLint, or manual review. Do not use for feature rewrites that change behavior; Chinese triggers include dead code, clean up unused, refactor clean, dependency cleanup, delete useless code.

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.

Knip dead code detection best practices for JavaScript and TypeScript projects. Use when configuring Knip, analyzing unused code, setting up CI integration, or cleaning up codebases. Triggers on knip.json, dead code, unused exports, unused dependencies, bundle optimization.

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

Use when working with Aws Idle Resources — detect unused and idle AWS resources that incur cost without providing value. Covers detached EBS volumes, idle load balancers, unused Elastic IPs, stopped EC2 instances, idle NAT Gateways, old snapshots, and unused ENIs. Includes estimated monthly waste per resource and anti-hallucination rules for safe detection.

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

Use when working with Gcp Idle Resources — detect unused and idle GCP resources that incur cost without providing value. Covers unattached Persistent Disks, unused external IPs, stopped VMs, idle Cloud NAT, idle load balancers, old snapshots, idle Cloud SQL instances, abandoned GKE node pools, unused VPC connectors, and orphaned Filestore instances. Includes estimated monthly waste per resource and anti-hallucination rules for safe detection.

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

Review Claude Code settings for duplicate skills, outdated memory files, unused permissions, and other clutter. The workflow presents evidence for each candidate, requests individual approval, and records reversible cleanup actions.

• Reviewing overlaps after installing many skills
• Checking outdated memory files and unused hooks
• Organizing duplicate permission entries

Inspect compressed JavaScript bundles, the files that package application code, to find excessive size and loading costs. Recommend splitting code, removing unused portions, and reviewing dependencies based on measured effects on page responsiveness.

• Finding JavaScript files over 200KB after compression
• Investigating delays before a page becomes interactive
• Reducing bundle size through code splitting

Check whether production JavaScript files are minified, meaning unnecessary characters are removed to reduce size. Review build settings and unused code removal, suggest configuration changes, and describe how to verify the resulting files in the browser.

• Check production JavaScript minification
• Review build settings for smaller files
• Remove unused code from bundles

Review JavaScript module usage and convert CommonJS code to ES modules using import/export. Inspect source code and browser execution, explain how unused code can be removed during builds, and describe how to verify changes.

• Converting require() calls to import statements
• Migrating module.exports to ES module exports
• Reviewing how browsers load modules

Audit CSS file sizes and loading behavior to find stylesheets that delay page rendering. Confirm the problem with performance measurements, then reduce unnecessary CSS through minification, unused-style removal, or splitting files by page.

• Investigating slow initial page rendering
• Finding oversized CSS files
• Removing unused styles and minifying CSS

Investigate Cherry Studio code to identify unused behavior, duplicated state, and unnecessary abstractions. Turn a few well-supported findings into cleanup proposals that document current consumers, removal scope, risks, and observable acceptance criteria.

• Finding unused code and unnecessary internal APIs
• Reviewing duplicated stores, caches, and events
• Assessing library replacements that reduce maintenance

Review changed code against project rules and report missing tests, unused code, typing problems, and style violations. It also checks API design and data isolation, helping developers identify issues after implementation.

• Reviewing changes after implementation
• Finding missing tests and unused code
• Checking Python types and API design

Analyze AWS spending by service, region, and resource tags to find unused resources and oversized configurations. Get specific cost reduction recommendations, estimated savings, and guidance for budgets and ongoing cost monitoring.

• Compare monthly AWS spending by service
• Find unused storage and idle instances
• Estimate savings from configuration changes

Review AWS spending and identify savings through resource sizing, unused resource cleanup, discount commitments, and storage policies. It also guides budget alerts and recurring cost reviews so teams can track spending and plan changes using usage data.

• Investigating an unexpected AWS bill increase
• Preparing cost reviews with engineering and finance
• Comparing Savings Plans and Reserved Instances

Plan periodic access reviews for AWS IAM, GitHub, Okta, and other identity systems. Provides guidance for identifying unused access, assigning reviewers, documenting approval or removal decisions, and organizing evidence for compliance audits.

• Planning periodic access reviews
• Reviewing inactive accounts and unused credentials
• Checking access against current job responsibilities