219건 · 관련도순
Automate Deadline Funnel operations through Rube MCP, a connection between an AI agent and external tools. Discover available tools, check the account connection, and run workflows using the current input requirements returned by tool search.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Explore unfamiliar code with Codebase Memory to map architecture, trace function calls and dependencies, and assess change impact. Findings are checked against source files, with index freshness and coverage considered before drawing conclusions.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Explore code structure and history using an index of code relationships and meaning-based search. Trace calls, assess change impact, find likely bug locations, generate architecture reports, and review pull requests for risk and conflicts.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
コードベースの不要なフォールバック・互換性コード・デッドコードを 3つの専門エージェント（scanner + historian + verifier）が協調して検出・安全性検証する監査スキル。 scanner が自律探索で候補を発見し、historian が git 履歴から時間軸の文脈を付与し、 verifier が「消してデグレしないか」を検証する。任意のリポジトリで実行可能。 Use when: コードのクリーンアップをしたい、技術的負債を可視化したい、 不要な互換性コードや deprecated コードを探したい、 リリース前に dead code を確認したい。 Triggers: "cruft", "code sweep", "dead code", "デッドコード", "不要なコード", "互換性コード", "fallback", "フォールバック", "deprecated", "技術的負債", "code audit", "コード監査", "cleanup", "クリーンアップ", "TODO整理"
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
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.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Run an automated codex⇄Claude debate to consensus — no round cap, no deadlock exit. Two explicit subcommands. `review` (also the bare/back-compat default) — codex (reviewer) critiques the current diff and a Claude subagent (author) fixes/disputes, looping until they agree. `answer` — Claude and codex each answer a freeform prompt in parallel, then cross-check until they agree, and a unified answer is returned. Use when the user types `/codex-debate`, asks to "have codex review this", "run the codex debate", "review this PR with codex", "argue this with codex until you agree", or passes a question to "have Claude and codex debate/answer until they agree".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
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.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Explore relationships between functions and files using a prebuilt code graph, a map of code dependencies. Trace bugs, inspect callers and execution paths, and assess the impact of refactoring or proposed changes.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Prepare a codebase for an external security review by defining goals, running static checks, improving test coverage, and removing unused code. Assemble the review scope, verified build instructions, diagrams, and documentation into a package for auditors.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Audit a codebase for unnecessary complexity, including dead code, duplicated state, redundant interfaces, and obsolete compatibility paths. Receive evidence-backed simplification candidates, or authorize changes that remove justified targets and validate the behavior that must remain.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
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.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
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.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Coordinates specialist agents in Claude Code to work from product requirements through design, implementation, testing, deployment, and operations. Includes task queues, saved progress, parallel reviews, and recovery workflows for managing extended development work.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Use when the user wants to simplify, clean up, refactor, tidy, or refine code — their staged/unstaged git changes or a target file/path. Reduces complexity, flattens nesting, removes redundancy and dead code, scores each change by value (holding low-value churn), then runs tests to prove nothing broke. Invoke on: "simplify", "simplify this", "simplify my code/changes", "clean up", "clean this up", "clean up my changes", "refactor this", "make this cleaner", "tidy this up", "reduce complexity", "flatten this", "remove dead code", "make it more readable", "polish before commit", or "absolute simplify". Acts on your working diff; for repo-wide dead code use absolute-prune; for lint/type debt use absolute-debt.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Detect technical debt — duplicated code, dead code, TODOs, and oversized functions across the codebase. Use at the end of a session or when auditing code hygiene. Trigger on "find tech debt", "any dead code", "duplicated code", "code hygiene", "techdebt".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Simplifies and refines code for clarity, consistency, and maintainability while preserving all functionality. Focuses on recently modified code unless instructed otherwise. This skill should be used when code-quality checks pass but the code would benefit from structural cleanup — deduplication, branching simplification, naming improvements, or dead-code removal. Invoked as a subagent from /code-quality or directly via the Task tool.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Review and simplify the ego-lite codebase by finding unused code, duplicated state, and unnecessary layers. The skill checks real callers and API requirements, explains behavior changes, and coordinates implementation, tests, and documentation updates.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Review the current codebase for ignored errors, embedded credentials, unused exports, and obvious type-safety gaps. Receive a report ordered by severity, with file and line references, while all source files remain unchanged.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Find and remove dead code (unused files, exports, class members) using Knip as a candidate generator, then verify each candidate through AST-level analysis and interface tracing before removing anything. Use when the user asks to clean up unused code, find dead code, or reduce the codebase.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
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.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Analyze indexed codebases via graph database (neug) and vector index (zvec). Covers call graphs, dependencies, dead code, hotspots, module coupling, architecture reports, semantic search, impact analysis, bug root cause from GitHub issues, class diagrams (UML), and PR review (risk scoring, conflict detection, auto-merge candidates, labeling). Also covers creating, inspecting, and repairing a CodeScope index. Use for: code structure, who calls what, why something changed, similar functions, module boundaries, bug tracing, class relationships, PR risk/conflicts, or any question benefiting from a code knowledge graph. Applies when a `.codegraph` index exists in the workspace, or when the user wants to create one.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Remove dead code, unused imports, fix lint warnings, and normalize formatting across a codebase without changing business logic or architecture. Use when lint warnings have piled up during rapid development, unused imports and variables clutter files, dead code paths were never removed, formatting is inconsistent, or static analysis tools report fixable hygiene issues.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Git-native issue tracking (beads), coding guidelines, knowledge injection, and spec-driven planning for AI agents. Drop-in replacement for bd/Beads with simpler architecture. Use for: tracking issues/beads with dependencies, creating bugs/features/tasks, planning specs, implementing features from specs, code reviews, committing code, creating PRs, loading coding guidelines (TypeScript, Python, TDD, golden testing, Convex, monorepo patterns), code cleanup, research briefs, architecture docs, agent handoffs, and checking out third-party library source code. Invoke when user mentions: tbd, beads, bd, shortcuts, issues, bugs, tasks, features, epics, todo, tracking, specs, planning, implementation, validation, guidelines, templates, commit, PR, pull request, code review, testing, TDD, test-driven, golden testing, snapshot testing, TypeScript, Python, Convex, monorepo, cleanup, dead code, refactor, handoff, research, architecture, labels, search, checkout library, source code review, or any workflow shortcut.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Git-native issue tracking (beads), coding guidelines, knowledge injection, and spec-driven planning for AI agents. Drop-in replacement for bd/Beads with simpler architecture. Use for: tracking issues/beads with dependencies, creating bugs/features/tasks, planning specs, implementing features from specs, code reviews, committing code, creating PRs, loading coding guidelines (TypeScript, Python, TDD, golden testing, Convex, monorepo patterns), code cleanup, research briefs, architecture docs, agent handoffs, and checking out third-party library source code. Invoke when user mentions: tbd, beads, bd, shortcuts, issues, bugs, tasks, features, epics, todo, tracking, specs, planning, implementation, validation, guidelines, templates, commit, PR, pull request, code review, testing, TDD, test-driven, golden testing, snapshot testing, TypeScript, Python, Convex, monorepo, cleanup, dead code, refactor, handoff, research, architecture, labels, search, checkout library, source code review, or any workflow shortcut.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.