remove-unused

Identify and remove dead code from codebases with test verification.

Updated Jun 25, 2026
One-click install
npx skills add https://github.com/YuriNakayama/neurogolf --skill remove-unused
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: remove-unused
Source: https://github.com/YuriNakayama/neurogolf/tree/main/.claude/skills/remove-unused
Command: npx skills add https://github.com/YuriNakayama/neurogolf --skill remove-unused

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill helps you safely identify and remove dead code from your codebase, reducing complexity and improving performance.

Core Features & Use Cases

  • Dead Code Analysis: Identifies unused code, exports, and dependencies.
  • Comprehensive Report: Generates a report detailing findings categorized by severity.
  • Safe Deletions: Proposes safe deletions based on analysis.
  • Test Verification: Ensures code removal does not affect functionality.

Quick Start

Use the remove-unused skill to analyze and clean up dead code in your project.

Frequently Asked Questions about remove-unused

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

FAQPage Schema
How do I automatically identify and remove dead code from my codebase?

To remove dead code safely, this skill scans your codebase for unused modules and exports, proposes safe deletions, and verifies that tests pass to ensure functionality without compromising system integrity.

What is dead code analysis and how does it help with software maintenance?

Dead code analysis identifies unused code, exports, and dependencies to reduce complexity and improve performance. It generates a comprehensive report of findings categorized by severity to guide safe code cleanup and software maintenance.

Does removing unused exports affect existing test functionality?

Removing unused exports does not affect test functionality when using safe deletion methods. This skill ensures code removal does not affect functionality by performing test verification after proposing safe deletions based on the dead code analysis.

Can I analyze code quality and clean up unused modules without breaking dependencies?

You can clean up unused modules without breaking dependencies by using safe deletion proposals. The analysis identifies unused code and dependencies, then relies on test verification to ensure system integrity is not compromised during the cleanup process.

What's the best way to generate a report of unused code categorized by severity?

The best way to generate a report of unused code is to run a comprehensive dead code analysis. This skill scans for unused modules and exports, producing a detailed report that categorizes findings by severity to help prioritize safe deletions.