spring-clean

Run tests, fix lint errors, and remove debug artifacts from codebases.

8|2|Updated Feb 18, 2026
One-click install
npx skills add https://github.com/DaccordProject/daccord --skill spring-clean
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: spring-clean
Source: https://github.com/DaccordProject/daccord/tree/main/.codex/skills/spring-clean
Command: npx skills add https://github.com/DaccordProject/daccord --skill spring-clean

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill guides and automates a thorough codebase cleanup by running tests, fixing lint errors, breaking down large files, and removing debug artifacts to keep the repository healthy and maintainable.

Core Features & Use Cases

  • Run unit tests to validate code health and catch regressions during cleanup.
  • Fix lint errors and improve code quality across the project.
  • Break down large files into smaller, more maintainable modules.
  • Remove leftover debug artifacts and streamline the repository for release.

Quick Start

Begin the cleanup by running the unit tests with ./test.sh unit and fix issues as you go.

Frequently Asked Questions about spring-clean

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

FAQPage Schema
How do I automate codebase cleanup to fix lint errors and remove debug artifacts?

You can automate codebase cleanup by running test scripts and lint tooling to fix errors, remove debug artifacts, and break down large files into maintainable modules for a healthy repository.

What's the best way to run unit tests during routine code maintenance?

The best way to run unit tests during code maintenance is executing your test scripts, such as ./test.sh unit, to validate code health and catch regressions as you fix issues and refactor.

Does this code cleanup workflow apply to both local development and CI pipelines?

Yes, this code cleanup workflow applies to routine maintenance across both local development workflows and CI pipelines, executing structured cleanup tasks to keep the repository streamlined for release.

How do I break down large files into smaller maintainable modules?

To break down large files into smaller maintainable modules, you apply structured refactoring tasks during the cleanup process, ensuring code quality improves while test validation prevents regressions.

What is structured codebase cleanup and when do I need it?

Structured codebase cleanup is an end-to-end process of running tests, fixing lint errors, and removing debug artifacts. You need it for routine maintenance to keep repositories healthy and maintainable before releases.