How does the Action skill ensure code safety?

The skill performs independent verification for every target using tools like ripgrep and import checks to ensure an item is truly unused before any removal action is taken.

Is there a limit to how many files can be removed at once?

Yes, to maintain safety and manual oversight, the skill is strictly limited to a maximum of 5 items per batch.

Can I use this for complex architectural refactoring?

This skill is specifically optimized for small, conditional cleanup tasks like removing unused files and dependencies rather than large-scale architectural changes.

Does the skill report what it skipped?

Yes, the skill provides a detailed report explaining which items were executed and which were skipped, including the specific reason for skipping an item.

Batch Code Cleanup

Name: Batch Code Cleanup
Author: jibaxZZZ

byjibaxZZZ

Developer Tools

Automates the safe removal of unused dependencies and redundant code through rigorous verification and batch processing.

About

The Action skill enables Claude to perform controlled, conditional cleanup tasks within a codebase, such as removing unused dependencies or dead code. By following a strict verification protocol involving ripgrep searches and import checks, it ensures that only truly redundant items are modified. This skill is particularly useful for maintaining project hygiene, reducing technical debt, and optimizing repository size while preventing accidental deletions through built-in safety limits and batch constraints.

Key Features

Minimizes technical debt by pruning unused project dependencies
Comprehensive reporting of executed vs. skipped actions
Automated verification of targets using ripgrep and import checks
Safety-first batching limited to 5 items per execution
Conditional execution that skips used items with detailed reasoning
0 GitHub stars

Use Cases

Removing redundant npm packages from package.json after a refactor
Deleting orphaned utility files or unused component exports
Cleaning up deprecated assets or configuration files across a project

About

Key Features

Minimizes technical debt by pruning unused project dependencies
Comprehensive reporting of executed vs. skipped actions
Automated verification of targets using ripgrep and import checks
Safety-first batching limited to 5 items per execution
Conditional execution that skips used items with detailed reasoning
0 GitHub stars

Use Cases

Removing redundant npm packages from package.json after a refactor
Deleting orphaned utility files or unused component exports
Cleaning up deprecated assets or configuration files across a project