analyze-dead-code
Find unused code, deprecated paths, and documentation drift. Use when cleaning up codebase, preparing for refactor, or auditing technical debt.
Works with
Agent Skills format with YAML frontmatter. Claude Code reads it as-is.
--- name: "analyze-dead-code" description: "Find unused code, deprecated paths, and documentation drift. Use when cleaning up codebase, preparing for refactor, or auditing technical debt." license: "MIT" --- # Analyze Dead Code Detect unused and deprecated code using the `dead-code-analyzer` agent. ## What It Finds 1. **Dead Code** - Functions, classes, modules, variables never used 2. **Deprecated Paths** - Code reachable but abandoned or marked for removal 3. **Documentation Drift** - Code that contradicts README, comments, or docstrings ## When to Use - "Clean up unused code" - "Is this function used anywhere?" - "Audit before major refactor" - "Check if docs match implementation" ## Output ``` ### Dead Code Inventory | Location | Type | Confidence | Notes | |----------|------|------------|-------| ### Deprecated Paths | Location | Pattern | Signal | Recommendation | ### Documentation Divergence | Documented Claim | Actual State | Severity | ### Summary - High confidence (safe to remove): X items - Medium confidence (verify first): X items - Priority actions: [list] ``` ## Agent Use `subagent_type: dead-code-analyzer`
More Refactoring skills
vercel-react-best-practices
vercel-labs/agent-skills
React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React/Next.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.
analyze-project
lllllllama/rigorpilot-skills
Rigor Analyze / Rigor Audit read-only skill for deep learning research repositories. Use when the user wants to read and understand a repository, inspect model structure and training or inference entrypoints, review configs and insertion points, or flag suspicious implementation patterns without modifying code or running heavy jobs. Do not use for active command execution, broad refactoring, speculative code adaptation, or automatic bug fixing.
request-refactor-plan
mattpocock/skills
Create a detailed refactor plan with tiny commits via user interview, then file it as a GitHub issue. Use when user wants to plan a refactor, create a refactoring RFC, or break a refactor into safe incremental steps.

