code-cleanup

Detect and prioritize code quality issues in Python and Go repositories.

415|44|Updated Mar 18, 2026
One-click install
npx skills add https://github.com/notque/claude-code-toolkit --skill code-cleanup-notque
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-cleanup
Source: https://github.com/notque/claude-code-toolkit/tree/main/skills/code-cleanup
Command: npx skills add https://github.com/notque/claude-code-toolkit --skill code-cleanup-notque

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Systematic detection and prioritization of neglected code quality issues: stale TODOs, unused imports, deprecated functions, high complexity, and dead code. This helps teams maintainable codebases by surfacing actionable debt and guiding targeted cleanup.

Core Features & Use Cases

  • Detects stale TODOs, unused imports, deprecated functions, high complexity, and dead code across repositories.
  • Prioritizes findings by impact and effort and provides time estimates for fixes.
  • Generates a structured, file-level report with exact file:line references to guide safe, user-approved changes.

Quick Start

Run a focused repository cleanup on a Python or Go project by asking me to scan for code quality issues in a targeted directory.

Frequently Asked Questions about code-cleanup

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

FAQPage Schema
How do I find dead code and unused imports in a Python or Go repository?

To find dead code and unused imports in Python or Go repositories, you can scan for code quality issues to detect neglected technical debt and produce a prioritized report with exact file:line references.

What is the best way to track stale TODOs and technical debt across a codebase?

Tracking stale TODOs and technical debt involves scanning your repository to surface neglected code quality issues. This process prioritizes findings by impact and provides time estimates to guide targeted cleanup efforts safely.

Can I use static analysis to detect high complexity and deprecated functions in Go?

Yes, static analysis can detect high complexity and deprecated functions in Go. The scan evaluates your project to identify these structural issues and generates a structured, file-level report with clear remediation guidance.

How do I prioritize code cleanup tasks when fixing technical debt?

Prioritize code cleanup tasks by generating a report that ranks findings by impact and effort. This provides time estimates for fixes and exact file:line references, guiding safe, user-approved changes for maximum maintainability.

Does this code cleanup scanning require any external linting dependencies?

No, this code cleanup scanning requires no external linting dependencies. It operates independently to detect issues like dead code and stale TODOs, producing a deterministic, structured report without needing additional tools installed.