'dead code' 검색 결과

Use when asking whether something in imp is actually finished - hunting stubs, placeholders, request fields that are parsed and then ignored, code paths or kernels that never run, gate-based features that silently no-op, tests that assert nothing. Triggers on "is this implemented", "unfinished", "stub", "placeholder", "dead path", "does this flag do anything", "accepted but ignored", "kernel never launched", "test asserts nothing", "neutral A/B on a gated feature". Do NOT use for structural debt / god files / duplication (codebase-audit) or for who-calls-what (code-graph).

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

Compiler-level code intelligence via native LSP — definitions, references, types, call hierarchies, and diagnostics.

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

Simplify working code while preserving behavior—remove dead paths, flatten nesting, clarify names, reduce duplication. Use after features work but code feels over-engineered.

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

Run a focused tech debt reduction sprint — inventories all technical debt (TODOs, outdated deps, missing tests, god objects), fixes code smells, removes dead code, then hardens with a review pass. Use when a codebase feels sluggish, before a major feature push, or on a regular maintenance cadence.

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

Run comprehensive code audit for architecture, dead code, and test quality. Use when reviewing overall codebase health, checking for architectural violations, or before marking a feature complete.

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

Checks unreachable code, unused imports/variables/functions, commented-out code, backward compatibility shims, deprecated patterns. Returns findings.

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

Perform comprehensive technical reviews of Ruby on Rails applications. Runs automated analysis tools (RubyCritic, Brakeman, bundler-audit, Gitleaks, Debride, linters, SimpleCov, Rails stats, Rails ERD), analyzes code for architecture, security, authorization (Pundit/CanCanCan), dead code, and design issues, and produces a structured markdown report with prioritized findings and a 0-10 score. Use when the user requests a tech review, code audit, project assessment, or quality analysis of a Rails application.

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

Audit agent runtimes and their tests for lifecycle inference, capability overload, context pollution, correlated verification, prompt-only control, false success, dead compatibility paths, test-only seams, and complexity without contribution. Use for whole-repository agent audits, slop or dead-code triage, test contribution reviews, large refactors, tool/context simplification, and cleanup requests that need proof before deleting code or tests.

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

Use when a diff needs a readability review — naming, single-responsibility, DRY, dead code, mismatch with codebase conventions — dispatched by /review-changes, /do-and-judge, /judge.

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

Route codebase-structure questions (who calls X, where used, change-impact) to an existing code-graph first: impact, tests-for, dead cheaper, never more precise; grep routine. Also 'call graph'.

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

Use when the user asks to verify a story or ticket implementation against its spec - per-AC verdicts, code reuse and design conformance, dead code, then adversarial maintainer verification. Requires the qa/review agent roles registered by scripts/install-codex.sh. Keywords: story QA, acceptance criteria, spec conformance, AC coverage, QA this branch, verify story.

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

Refactor code to remove dead code, useless comments, unused variables, and unused imports. Use when asked to declutter a class, clean up noisy code, remove cruft, or run `/refactor:declutter`.

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

Survey a codebase's animation and motion code as a senior motion advisor, then produce a prioritized audit and self-contained implementation plans for other agents (or cheaper models) to execute. Read-only on source code — it plans improvements, it does not apply them. Use when the user asks to "improve the animations", "audit the motion", "make this app feel better", or wants a roadmap of animation fixes rather than a review of a single diff.

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

Solidity 자동화 마켓 메이커와 유동성 풀을 점검합니다. 체크리스트와 구현 예제로 재진입 공격, 지분·가격 조작, 교환 한도, 정수 연산, 관리자 권한을 검토합니다.

• 유동성 풀 계약 감사
• 입출금 지분 계산 검토
• 교환 최소 수령량과 기한 제한

Analyze malware communication with command servers to understand periodic check-ins, message formats, encoded data, and backup destinations. Produces a structured analysis report and network detection rules based on captured traffic and malware code.

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

• Investigating malware communication in captured traffic
• Measuring periodic check-in intervals and timing variation
• Mapping command servers and backup destinations

Review a development milestone using sprint reports, feature status, bugs, and risks. Summarize completion, quality, and delivery pace, then recommend whether to proceed, proceed with conditions, or stop, with scope choices and action items.

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

• Reviewing progress before a milestone deadline
• Identifying blockers and quality risks
• Choosing features to protect or defer

Read PDFs, Office files, web documents, and large text files to answer questions, summarize content, compare sources, or extract tables and key points. Use OCR, text recognition from images, when vision tools cannot read document text.

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

• Find conclusions and deadlines in a report
• Compare requirements across document versions
• Extract text from scans when vision tools fail

Provides a reference for reviewing DeFi smart contracts, programs that manage blockchain transactions. It organizes vulnerability types with causes, code examples, search patterns, and fixes to help investigate accounting, permissions, boundary conditions, and pricing logic.

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

• Checking for accounting inconsistencies and missing permission checks
• Comparing normal and alternative code paths
• Reviewing deadline and array boundary conditions

Turn meeting transcripts, rough notes, or long meeting chats into structured notes with decisions, open questions, risks, and action items. Include task owners and deadlines, with an optional short summary for Slack or email.

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

• Turn meeting transcripts into shareable notes
• Organize decisions and unresolved questions
• Extract tasks with owners and deadlines

Help an agent run terminal commands, follow long-running jobs, retrieve logs, and cancel work. It explains result fields, execution deadlines, retained output, and operating-system differences so the agent can interpret command outcomes and choose appropriate tools.

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

• Track a build that continues in the background
• Retrieve command output omitted from the initial response
• Check command outcomes beyond numeric exit codes

Create and manage tasks and task lists in 飞书. Assign people, set deadlines, find unfinished work, mark tasks complete or reopen them, and control list membership for collaboration within your access permissions.

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

• Create tasks with assignees and deadlines
• Review unfinished tasks
• Mark tasks complete or reopen them

Review mock configurations in .NET tests by tracing the production code each test exercises. Identify unused, unreachable, duplicated, or replaceable setups, explain concrete fixes, and distinguish them from appropriate mocks for databases, HTTP clients, and other external services.

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

• Finding unused or unreachable mock setups
• Consolidating duplicated mock configurations
• Reviewing ILogger and IOptions replacements

Use this skill to run a holistic regrounding pass on the entire microsoft/apm documentation corpus against current source code, page-by-page, and emit surgical fixes for stale claims. Activate when the maintainer wants a WHOLE-CORPUS audit (not per-PR review) -- typical triggers include "audit the docs", "reground the corpus", "check every page against code", "pre-release docs sweep", "the docs have drifted everywhere", or "we just reshaped the TOC, find dead links". Wave-batched and S7-verified; scales to the full ~112-page corpus in ~10 minutes wall-time. This is a SIBLING to docs-sync, not a replacement: docs-sync is per-PR (triggered by a diff); this skill is per-corpus (triggered by a maintainer ask). They share agent personas, schemas, and the docs index, but their triggers MUST NOT collide. Does NOT auto-merge, does NOT push without maintainer review, and does NOT replace per-PR drift detection.

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

Troubleshoot Golang programs systematically - find and fix the root cause. Use when encountering bugs, crashes, deadlocks, races, or unexpected behavior in Go code. Covers debugging methodology, common Go pitfalls, test-driven debugging, pprof setup and capture, Delve, race detection, GODEBUG tracing, and production debugging. Start here for any 'something is wrong' situation. Not for interpreting profiles or benchmarking (→ See `samber/cc-skills-golang@golang-benchmark` skill), applying optimization patterns (→ See `samber/cc-skills-golang@golang-performance` skill), or designing new code (→ See `samber/cc-skills-golang@golang-safety` skill for defensive coding, `samber/cc-skills-golang@golang-concurrency` skill for concurrency design).

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