cleanup

To clean up a project repository before a pull request, remove temporary files, obsolete debug code, and outdated documentation. This ensures that your commits remain professional and adhere to coding standards prior to submission.

The best way to remove obsolete code and outdated documentation is to use an automated cleanup workflow. This process eliminates unused files, resolves handled TODOs, and aligns docs with the final implementation state.

Code cleanup and repository hygiene should be performed immediately after feature verification and before pushing changes. This ensures functional integrity is maintained by removing residual artifacts right before commit preparation.

Repository cleanup does not break your test suite if executed correctly. It removes extraneous files and commented-out code, then runs a full test suite execution to verify functional integrity and ensure no functionality is broken.

Yes, you can use a cleanup skill to align project documents with your final code implementation. It updates outdated documentation to match the finalized implementation, ensuring documentation accuracy after development.