code-janitor

Automate code cleanup and production-readiness verification across codebases.

88|9|Updated Jul 16, 2020
One-click install
npx skills add https://github.com/docs-plus/docs.plus --skill code-janitor
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-janitor
Source: https://github.com/docs-plus/docs.plus/tree/main/.cursor/skills/code-janitor
Command: npx skills add https://github.com/docs-plus/docs.plus --skill code-janitor

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates the tedious, inconsistent manual work of cleaning up messy codebases, ensuring code meets production-ready standards without hours of unguided review.

Core Features & Use Cases

  • 5-Stage Cleanup Pipeline: Automatically groups files by intent, then runs a sequential simplification → abstraction → readability → documentation → production-readiness sweep, with a supervisor granting an industry-standard production-ready flag only when all checks pass.
  • Common Cleanup Tasks: Handles fixing typos in identifiers, splitting overgrown files, improving JSDoc, removing dead code, and strengthening weak typing without altering runtime behavior.
  • Use Case: If you just finished a feature branch with messy helper functions, duplicated logic, and missing docs, use this Skill to tidy the code and get an industry-standard production-ready flag.

Quick Start

Use the code-janitor skill to clean up your project's code and get a production-ready readiness verdict.

Frequently Asked Questions about code-janitor

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

FAQPage Schema
How do I automate code cleanup and verify production-readiness for a messy codebase?

Automate code cleanup using a 5-stage pipeline that sequentially simplifies, abstracts, improves readability, adds documentation, and verifies production-readiness. It groups files by intent and grants a production-ready flag only when all quality gates pass.

What is the best way to remove technical debt and dead code before deploying to production?

Remove technical debt by running an automated cleanup sweep that eliminates dead code, fixes identifier typos, and strengthens weak typing. This process enforces coding standards without altering runtime behavior before deployment.

How does code refactoring work for recent git changes without altering runtime behavior?

Code refactoring for recent git changes works by polishing the modifications through a sequential pipeline that handles tidying utility folders, splitting overgrown files, and improving documentation while preserving the original runtime behavior.

Can I use an automated code review tool for codebases of any size and tech stack?

Yes, you can use this code review and cleanup tool for codebases of any size or tech stack. It applies a consistent, principle-driven workflow to validate code for production deployment across different technologies.

When do I need to run a production-readiness verification sweep on my feature branch?

Run a production-readiness verification sweep when you finish a feature branch containing messy helper functions, duplicated logic, and missing docs. It tidies the code and outputs an industry-standard production-ready verdict.

What are the limitations of automated code cleanup for improving JSDoc and splitting files?

Automated code cleanup focuses on tidying code, improving JSDoc, and splitting overgrown files, but it does not alter runtime behavior. It is limited to enforcing coding standards and removing technical debt through a principle-driven workflow.