dedup-code-agent

Detect code duplication, dead code, and dependency bloat in software projects.

Updated Feb 26, 2026
One-click install
npx skills add https://github.com/natslash/options-strategy-builder --skill dedup-code-agent-natslash
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dedup-code-agent
Source: https://github.com/natslash/options-strategy-builder/tree/main/.claude/skills/dedup-code-agent
Command: npx skills add https://github.com/natslash/options-strategy-builder --skill dedup-code-agent-natslash

SYSTEM DOCUMENTATION & REQUIREMENTS

## What problem does it solve? Detects code duplication, dead code, and dependency bloat to improve code quality and maintainability across projects.

## Core Features & Use Cases

  • Discover: map project structure, shared utilities, and test coverage
  • Scan: multi-phase analysis to find duplicates, dead code, and unused dependencies
  • Classify: severity-based reporting (Critical / Warning / Suggestion)
  • Report: structured results with file locations, counts, and actionable recommendations
  • For complete methodology: read reference/dedup-analysis-methodology.md

### Quick Start Run the dedup-code-agent on your codebase to generate a deduplication report.

Frequently Asked Questions about dedup-code-agent

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I find code duplication and dead code in a Flutter project?

To find code duplication and dead code in a Flutter project, use a static analysis agent that scans your codebase to map project structure, detect duplicated blocks, and identify unused files across libraries and modules.

What is the best way to detect unused dependencies and technical debt in a Firebase codebase?

Detecting unused dependencies and technical debt in a Firebase codebase requires multi-phase scanning that classifies dependency bloat by severity. This produces a structured deduplication report detailing file locations, counts, and recommendations for removal.

Can I use static analysis to check for dead code across multiple libraries and modules?

Yes, you can use static analysis to check for dead code across multiple libraries and modules. The scanning process evaluates shared utilities and test coverage to identify unused code blocks spanning your entire project structure.

Does code duplication analysis require any specific test coverage setup before scanning?

Code duplication analysis maps existing project structure and test coverage during its discovery phase without requiring specific prior setup. It evaluates shared utilities directly from the codebase to detect unused dependencies and duplicated code.

How are duplicated code blocks classified and reported by static analysis tools?

Duplicated code blocks are classified by severity into Critical, Warning, or Suggestion categories. The reporting phase outputs a structured deduplication report containing exact file locations, occurrence counts, and actionable recommendations for resolving technical debt.