219건 · 관련도순
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.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
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.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Find unused components, files, translation keys, and other unnecessary code across a codebase. Document every consumer and removal impact in a tracking issue, then turn one maintainer-approved candidate into a focused pull request.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Review code for privacy risks, prepare data protection impact assessments, and track personal data requests and deadlines. The skill supports GDPR and German privacy compliance work, with final compliance decisions referred to a data protection officer or legal counsel.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Find unused functions and dead code in the codebase
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Find unused functions and dead code in the codebase
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Dead code and dependency cleanup, repo-wide: unused deps, unreferenced exports, unreachable code, orphaned files — removed only with tool evidence, in reversible waves. Runs on green main. For diff-scoped cleanup use absolute-simplify. Triggers on "absolute prune", "remove dead code", "find unused deps/exports", "what can we delete", "clean up orphaned files".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when verifying a story or ticket implementation against its spec and acceptance criteria - per-AC verdicts with file:line evidence and proving tests, code reuse and design conformance, dead code, stale docs, comment discipline. Finds the spec from an explicit path, the ticket key in the branch name, or plan files - and asks rather than guessing. For defect-hunting code review use dotnet-techne-code-review instead. Keywords: story QA, acceptance criteria, spec conformance, AC coverage, definition of done, dead code check, reuse check, comment check, verify story, QA this branch.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Remove signs of AI-generated code from a codebase while preserving behavior. Use when editing or reviewing code to make it read like a human engineer on this team wrote it. Works through a test-guarded detect-modify-verify loop: pin down the functional contract and edge cases first, write or run tests as a safety net, then rewrite AI tells (redundant comments, emoji, verbose names, reflexive try/except, defensive null-guards, over-decomposition, speculative abstraction, dead code, non-idiomatic constructs, hallucinated dependencies) and re-verify after every change. The tests decide whether a defensive block is slop or a real safeguard.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Clean up AI-generated code in branch changes or selected files while preserving behavior. Establish passing regression tests first, then remove unnecessary code and complexity, run project quality checks, and report both changes and skipped issues.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Document a local codebase with file references, architecture diagrams, and verified project commands. For legacy modernization, assess what still runs and create a phased migration plan with validation methods suited to each component’s current condition.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Simplify bloated AI-generated code by removing dead code, duplicated logic, and unnecessary layers while checking that existing behavior stays intact. Use a limited cleanup scope, verify changes with relevant checks, or request a review without edits.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Review a diffusers contribution before opening a pull request. Check the full change against project rules, trace potentially unused code, and receive a severity-based report separating required fixes from points to discuss with reviewers.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Clean up working code by identifying duplication, dead code, unnecessary layers, and error paths that hide failures. Preserve behavior with targeted tests, simplify the requested files in stages, and report verification results and remaining risks.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Model distributed systems and concurrent algorithms in TLA+ or PlusCal, then check possible states with TLC. Use the results to investigate deadlocks, broken rules, and differences between specifications and implementation code.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Simplify code that works — remove speculative abstraction, dead flexibility, and needless indirection while keeping behaviour identical and verified. Use when a feature has just landed ('now simplify it'), when AI-generated code arrives over-engineered, when a file has grown hard to follow, or as the cleanup pass before review. Produces a smaller, flatter version with identical behaviour, plus a ledger of what was removed and why it was safe. For finding bugs use code-review-checklist / ai-code-review — this skill assumes it works and makes it simple.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Simplification audit or authorized codebase simplification whose stated objective is to remove accidental complexity. Use for evidence-backed deletion or consolidation of dead code, duplicate state, redundant APIs or layers, ownerless abstractions, obsolete compatibility or design records, and over-engineering in any language; also use for 代码简化 or 熵回收. Do not use for general code review, onboarding, style-only refactoring, or performance tuning.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Automatically repair C/C++ code violations detected by TLA+ model checking. Takes a program, TLA+ specification, and TLC counterexample trace as input, then generates minimal code modifications to eliminate the violation. Use when: (1) TLC model checker reports an invariant violation, deadlock, or temporal property failure, (2) You have a counterexample trace and need to fix the corresponding code, (3) You need to understand how a TLA+ violation maps to program-level bugs, (4) You want to validate repairs by re-running TLC. Supports safety properties (invariants), liveness properties (temporal logic), and deadlock detection.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Audit experiment integrity against the evidence ledger. At L2 (repo + result files present) a fresh cross-model reviewer reads the eval code line-by-line for fake/derived ground truth, score self-normalization, phantom results (a paper number with no backing file/key), dead/uncalled metric code, verified-scope inflation, method-described ≠ method-evaluated drift, synthesized-looking results, placeholder/fake data still wired into a released result, code-output ≠ reported-number mismatch, and missing reproducibility artifacts (an empirical/agent/LLM paper shipping neither code nor the prompts/configs its results need) — every finding span-anchored to a ledger claim_id. At L0/L1 (PDF / source only) the same patterns are surfaced as info-level 'could-not-verify' signals where the ledger gives an anchor (observability_level_required:2) — NEVER a fraud verdict from a PDF. The reviewer PROPOSES findings; tools/adjudicate_findings.py computes the verdict. Detect-only. Triggers: "experiment forensics", "audit the results", "check the eval code", "实验诚实度".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when auditing the imp codebase for structural debt, dead code, god-objects/files, duplication, flag sprawl, or deciding whether a cleanup is worth shipping - "structure audit", "tech debt", "is this still used", "dead code", "refactor for clarity", "should we split this file", "remove this flag", "file size gate red", "alloc sites gate red". Do NOT use for build/test mechanics (building-and-testing), perf/kernel work (benchmark-cuda / sm120-cuda-expert), or output quality (check-degeneration).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Extract maximum value from existing code — performance optimization, API surface refinement, and dead weight elimination. The art of turning base code into gold through systematic identification and amplification of value-bearing patterns. Use when optimizing a working but sluggish codebase, refining an API surface that has accumulated cruft, reducing bundle size or memory footprint, or preparing code for open-source release — when code works correctly but doesn't shine and needs polish rather than a full rewrite.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Two-agent cleanup pattern. Implementer works freely, then a dedicated cleanup agent removes unused imports, console.logs, commented-out code, dead code, and formatting issues. Produces a diff of what was cleaned.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Python code quality review lens. SOLID principles, dead code, exception handling, resource leaks, thread safety, performance. Triggered by "quality" ("품질"), "SOLID", "dead code" ("데드코드"), "exception", "resource leak", "thread safety" keywords.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Codebase audit + refactoring workflow. Dead code detection, God Object splitting, duplicate function removal, design flaw identification, frontier comparison verification. Triggered by "audit" ("감사"), "dead code" ("데드코드"), "refactor" ("리팩토링"), "god object", "duplication" ("중복"), "design flaw" ("설계 결함") keywords.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.