cleanup-code

Automate linting and automatic fixes until all checks pass.

5|Updated Aug 28, 2025
One-click install
npx skills add https://github.com/agnesk92/macos-setup --skill cleanup-code-agnesk92
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cleanup-code
Source: https://github.com/agnesk92/macos-setup/tree/main/dotfiles/claude/.claude/skills/cleanup-code
Command: npx skills add https://github.com/agnesk92/macos-setup --skill cleanup-code-agnesk92

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates linting and automatic fixes to reduce recurring code quality issues across software projects.

Core Features & Use Cases

  • Automated Linting: Run standard lint suites and report failures.
  • Automatic Fixes: Apply fixes where possible and re-run checks.
  • Iterative Cycle: Repeat up to five iterations until all checks pass or issues are resolved.

Quick Start

Run the lint cycle on your project to automatically detect and fix issues until all checks pass.

Frequently Asked Questions about cleanup-code

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

FAQPage Schema
How do I automate lint fixes for recurring code quality issues?

Automate lint fixes by running a deterministic lint-fix cycle that applies non-ignoring fixes and re-runs checks up to five iterations until all linters pass or issues are resolved.

What is an iterative lint-fix cycle and when do I need it?

An iterative lint-fix cycle repeatedly applies automatic fixes and validates code until checks pass or five iterations are reached. You need it to reduce recurring code quality issues across software projects.

How do I run automated code cleanup that stops when all lint checks pass?

Run automated code cleanup through a guarded workflow with explicit validation that repeats linting and fixes until all checks pass or the five-iteration limit is reached, transparently reporting failing and fixed linters.

Can I use automated lint fixes on any software project without extra dependencies?

Yes, you can use automated lint fixes on typical software projects without extra dependencies, as the workflow runs standard lint suites, applies fixes, and reports results with no required setup components.

What happens if automatic fixes do not resolve all lint failures after five iterations?

If automatic fixes do not resolve all lint failures after five iterations, the guarded workflow stops and transparently reports the remaining failing and fixed linters for manual review.

What's the best way to ensure lint fixes do not ignore underlying code issues?

The best way to ensure lint fixes address underlying issues is using a guarded workflow with explicit validation that applies non-ignoring fixes and transparently reports both failing and fixed linters after each iteration.