cleaning-up

Assess and clean codebases by archiving dead code and running tests.

1|Updated Jan 31, 2026

Search Tags:#automation #refactoring #code maintenance #dead code #code hygiene #code cleanup

Ready to run

npx skills add https://github.com/jugrajsingh/skillgarden --skill cleaning-up

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: cleaning-up
Source: https://github.com/jugrajsingh/skillgarden/tree/main/plugins/tidyup/skills/cleaning-up
Command: npx skills add https://github.com/jugrajsingh/skillgarden --skill cleaning-up

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the process of identifying and cleaning up various forms of code and documentation "clutter" within a codebase, ensuring a more maintainable and efficient project.

Core Features & Use Cases

Automated Assessment: Analyzes the codebase for dead code, duplicate code, and stale documentation.
Guided Cleanup: Presents findings to the user for explicit approval before any modifications are made.
Safe Archiving: Never deletes files; instead, it archives stale content, ensuring zero information loss.
Verification: Runs the project's test suite after cleanup to ensure no functionality was broken.
Use Case: After a large feature merge, use this Skill to identify and safely remove unused imports, commented-out code blocks, and old documentation files that are no longer relevant.

Quick Start

Run the cleaning-up skill to assess and clean the entire codebase.

Frequently Asked Questions about cleaning-up

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

FAQPage Schema

How do I safely remove dead code and duplicate functions from my codebase?▼

To safely remove dead code and duplicates, this Skill executes a comprehensive cleanup workflow that assesses the codebase, guides you through explicit approval for removals, and archives stale content to ensure zero information loss.

What is the best way to clean up old documentation and unused imports after a large feature merge?▼

The best way to clean up post-merge clutter is running an automated assessment that identifies unused imports, commented-out code blocks, and old documentation, presenting findings for your explicit approval before archiving.

Can I automate code hygiene and refactoring without risking broken functionality?▼

Yes, you can automate code hygiene without breaking functionality because the workflow verifies all changes by running the project's existing test suite after archiving stale content and consolidating duplicates.

Does the code cleanup process permanently delete files when removing stale content?▼

The code cleanup process does not permanently delete files; instead, it performs safe archiving of stale content and removed code blocks to ensure zero information loss during the refactoring workflow.

How do I assess my entire project for code maintenance issues like duplicate code?▼

You assess your entire project by running an automated analysis that scans for dead code, duplicate functions, and stale documentation, generating detailed reports on actions taken and cleanup metrics.