janitor

Automated code cleanup applies isolated fixes in a throwaway git worktree off main, ensuring your primary working tree remains untouched. It surveys the repository, applies verifiable changes, and opens a pull request for manual review.

Safe codebase cleanup identifies low-risk maintenance tasks like lint-format, dead-code, and whitespace-eof-imports, then applies them in an isolated git worktree with strict boundary checks and fail-closed behavior before opening a pull request.

Yes, you can run automated repository cleanup in a zero-prompts mode by invoking the autonomous flag. This executes the full survey-to-pull-request pipeline without operator interaction while maintaining fail-closed safety gates.

A git worktree creates a separate isolated working directory off the main branch, applying cleanup changes there without modifying your primary checkout. This isolation prevents uncommitted work from being affected by automated maintenance scripts.

Automated cleanup operates under a strict batch limit and only handles v1 categories: lint-format, dead-code, and whitespace-eof-imports. It requires predefined boundary standards and fail-closes on any errors encountered during the pipeline.

Yes, automated code cleanup requires predefined trust rules and boundary standards to verify selected fixes. These rules ensure the pipeline only applies small, deterministic changes that pass verification gates before opening a pull request.