Code Cleanup Skill

Automated code review and refactoring analyzes uncommitted and outgoing Git commits to improve readability, performance, and Pythonic practices without introducing breaking changes. It validates code against established architectural patterns and applies structural improvements.

Adding Google-style docstrings is handled by documentation generation features that automatically analyze Python classes and methods. This process adds standardized documentation to your code, ensuring consistency and improving maintainability before merging new features.

Yes, code cleanup works directly with uncommitted changes and outgoing commits in a Git branch. It reviews these changes to ensure alignment with project coding standards and applies refactoring improvements without introducing breaking changes.

Ensuring code alignment with Pipecat's architecture involves reviewing changes for correctness, performance, and consistency against established patterns. This approach validates services, pipelines, and examples to maintain high code quality and architectural adherence.

Yes, you can refactor code for readability and performance without introducing breaking changes. The cleanup process focuses on improving code structure, naming conventions, and Pythonic practices while validating against established patterns for services and pipelines.

You should run code cleanup before merging a new feature to automatically clean up the code, add necessary documentation like Google-style docstrings, and ensure alignment with established project patterns, saving developer time and improving maintainability.