sc-improve

Refactor codebases to improve quality, performance, and maintainability.

19|2|Updated Aug 26, 2025
One-click install
npx skills add https://github.com/Tony363/SuperClaude --skill sc-improve-tony363
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sc-improve
Source: https://github.com/Tony363/SuperClaude/tree/main/.claude/skills/sc-improve
Command: npx skills add https://github.com/Tony363/SuperClaude --skill sc-improve-tony363

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill addresses code quality, performance bottlenecks, maintainability issues, and cleanup tasks, ensuring a more robust and efficient codebase.

Core Features & Use Cases

  • Systematic Code Improvement: Applies improvements across quality, performance, maintainability, and style.
  • Automated Cleanup: Removes dead code, unused imports, and optimizes file structures.
  • Use Case: Refactor a legacy module to improve its readability and reduce its complexity, ensuring all existing functionality remains intact.

Quick Start

Apply systematic improvements to code quality for the src directory using safe mode.

Frequently Asked Questions about sc-improve

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

FAQPage Schema
How do I refactor a legacy module to improve readability without breaking existing functionality?

To refactor a legacy module safely, apply systematic code improvement focused on complexity minimization and functional preservation, using safety validation to ensure existing functionality remains fully intact.

What is the best way to remove dead code and organize imports across a codebase?

Automated code cleanup removes dead code and unused imports while optimizing file structures, systematically addressing technical debt reduction and maintainability across the entire codebase.

How does code improvement handle performance optimization and maintainability simultaneously?

Code improvement applies multi-persona expertise to address performance bottlenecks and maintainability issues concurrently, ensuring a more robust and efficient codebase through systematic refactoring.

Can I use safe mode to reduce technical debt in a specific directory without causing regressions?

Yes, you can apply systematic improvements to code quality for a specific directory using safe mode, which enforces safety validation and functional preservation while reducing technical debt.

When should I not use automated refactoring for cleaning up a codebase?

Avoid automated refactoring when functional preservation cannot be guaranteed through safety validation, as removing dead code or optimizing performance without validation risks breaking existing functionality.