'dead code' 검색 결과

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.

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

Deep codebase cleanup — kills dead code, fixes all lint/format warnings, removes orphaned files, cleans stale TODOs, strips security hazards, tightens TypeScript strict mode, and organizes imports. Triggers: clean up, dead code, unused imports, lint, technical debt cleanup.

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

Execute a bounded ClawJS/Clawix code hygiene cleanup campaign from an audit report, one category and repo at a time.

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

Code quality dashboard. Wraps existing project tools (type checker, linter, test runner, dead code detector, shell linter), computes a weighted composite 0-10 score, and tracks trends over time. Use when: "health check", "code quality", "how healthy is the codebase", "run all checks", "quality score". (gstack)

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

Pre-PR code review checklist for this repo. Plan alignment, security gates, layering, dead code, API-surface completeness. Used by the code-reviewer agent.

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

Search Denmark’s official Jobnet.dk portal by occupation, region, distance, working hours, or employment duration. Retrieve full job descriptions, employer contacts, deadlines, and application links, and explore Danish job titles to refine searches.

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

• Finding Danish jobs by occupation and region
• Searching within a set distance of a postal code
• Filtering by working hours and employment duration

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

Evaluate job offers by separating guaranteed pay, conditional bonuses, and estimated equity value. Compare terms, develop an evidence-based counteroffer, draft emails and call scripts, rehearse recruiter conversations, and prepare deadline extensions, acceptance, or decline messages.

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

• Comparing pay and terms across job offers
• Drafting a counteroffer email
• Rehearsing a salary negotiation call

Inventory feature flags, switches that control feature availability, and remove eligible flags with their unused code branches. Leave ongoing rollouts and experiments untouched, run verification checks, and prepare a pull request for human review.

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

• Removing flags after a feature has fully rolled out
• Cleaning up unused flags and unreachable code branches
• Listing ongoing rollouts and experiments for human review

Turn Granola meeting notes into concrete follow-up work by identifying the user's commitments, owners, deadlines, and supporting passages. Make code changes, create tickets through connected tools, or draft replies, with each action traced to its source.

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

• Identify personal commitments after a meeting
• Implement code changes agreed in a meeting
• Create tickets from meeting commitments

Token-efficient code analysis via 5-layer stack (AST, Call Graph, CFG, DFG, PDG). 95% token savings.

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

Token-efficient code analysis via 5-layer stack (AST, Call Graph, CFG, DFG, PDG). 95% token savings.

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

Use when you need to apply Java concurrency best practices — including thread safety fundamentals, ExecutorService thread pool management, concurrent design patterns like Producer-Consumer, asynchronous programming with CompletableFuture, immutability and safe publication, deadlock avoidance, virtual threads, structured concurrency, scoped values, backpressure, cancellation discipline, and observability for concurrent systems. This should trigger for requests such as Review Java code for concurrency; Review Java code for thread safety; Fix race conditions in Java concurrency code; Choose ExecutorService or virtual threads in Java; Improve synchronization and shared mutable state handling; Apply structured concurrency for related Java subtasks. Part of Plinth Toolkit

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

Detects codebase bloat via dead code, duplication, complexity, and doc bloat scans. Use when codebase feels large or before a release.

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

Investigate how a concept, code path, application, network flow, system, incident, document, or local artifact actually works, then deliver a two-depth visual HTML explainer with a dead-simple big-picture first layer and source-backed technical depth behind it. Use when the user invokes $xray, asks how something works under the hood, wants a module or app behavior traced across boundaries, requests web, code, network, or safe static artifact research before explanation, or asks for an evidence-backed explainer. Do not use for answer-only definitions, general web design, full codebase audits, or invasive binary reverse engineering without explicit authorization.

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

Recover Vine video metadata (author, user ID, title, thumbnail) from vine.co oembed endpoint even though the Vine API and pages are dead. Use when: (1) you have Vine shortcode URLs (vine.co/v/XXXXX) and need to identify the creator, (2) the Vine page only shows a loading spinner, (3) archive-api.vineapp.com returns 404, (4) need to map Vine shortcodes to user IDs for cross-referencing against the divine.video database. The oembed endpoint is a still-live metadata oracle for the otherwise-dead Vine platform.

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

Dead code removal via parallel scanning, reference verification, batch execution, and atomic commits. You are the ORCHESTRATOR — you scan, verify, batch, then delegate ALL removals.

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

Edit, trim, cut, caption, subtitle, reframe, combine, add background music to, or export video, audio, and image files through Cassette. Use this skill whenever the user asks to change, preview, or render a media file in the project — even if they never say "Cassette" or name a tool — for example "trim the intro off demo.mp4", "add subtitles to this clip", "make me a 30-second cut with music", "why is there dead air at the start". Drives the local Oh My Cassette stdio MCP tools in Codex or Claude as one multi-turn conversation with the Cassette agent, with per-turn timeline previews, guided questions, and rendering only on explicit export.

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

Simplifies recently changed or explicitly scoped code while preserving observable behavior, error semantics, side effects, ordering, and public contracts. Use for readability cleanup, dead-code removal, reducing nesting, eliminating redundant wrappers, or making an implementation easier to maintain. Not for architecture redesign, new behavior, speculative cleanup, or a refactor without an adequate safety net.

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

Improve existing code without changing behavior: scan smells, simplify, dedupe, reuse utilities, and verify after edits. Use for refactor, cleanup, simplify, reduce duplication, extract method, dead code, or code smells. No PR.

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

Full codebase health assessment. Use when diagnosing project health or starting a rescue workflow on legacy code — OR when evaluating an external GitHub repo for dependency / fork / contribution decisions (--external mode). Analyzes complexity, dependencies, dead code, tech debt, and git hotspots. Produces a health score and rescue plan.

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

Detects common LLM coding agent artifacts in codebases. Identifies test quality issues, dead code, over-abstraction, and verbose LLM style patterns. Use when cleaning up AI-generated code or reviewing for agent-introduced cruft.

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

Expert guide for in-memory Abstract Syntax Tree (AST) code knowledge graphs, real-time symbol dependency mapping, refactoring blast radius calculation, and dead code eradication / Panduan ahli graf pengetahuan AST kode in-memory, pemetaan dependensi simbol real-time, kalkulasi radius dampak refaktor, dan pembersihan kode mati.

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

Use before opening a PR, or whenever asked to self-review a diffusers contribution. Applies the same rubric as the `@claude` CI (checks the diff against references/review-rules.md, traces call paths for dead code). Reports findings grouped by severity, flagging what to fix before submitting (blocking issues + dead code) vs what to leave for the actual review. Report-only — does not edit files.

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