# commiter

> A rust program to ensure the quality of commit

- Authors

  - Willy Micieli

- Immediate goals, but is necessary for long-term progress

- Code cleanup and maintenance

- Initial commit or major feature start

- Reduction of codebase size or removal of features

- Merging features or components

- Removing large chunks of code or features

- Undeveloped feature with potential

- Bug fix or error resolution

  - pull modifications before send

- Initial implementation of a feature

- Connecting code parts

- Fixing unknown or mysterious bugs

- Minor updates or fixes

- Comprehensive optimization of a specific area

- Scaling up the system or increasing capacity

- Initial integrations with external systems

- Long-term project for a self -sustaining system

- Collection of related changes

- Altering data or information flow

- Slowing down or reducing code performance

- Resolving merge conflicts or dependencies

- Removing technical debt

- Improving documentation or communication

- Migration to a new architecture or language

- Stabilizing or balancing code parts

- Deploying to production or releasing a version

- Significant performance improvements

- Temporarily disabling a feature

- Minor, temporary change

- Series of small changes or fixes

- Project management changes

- Represents project management-related changes

- Celebrates the completion of major milestones

- Major milestone or goal completion

- Code refactoring

  - use workspace

- Optimizing code for performance

- Changing project direction

- Brings the project closer to its goals or objectives

- Removal or deprecation of a component

- Performance improvement

- Establishing close relationships between code parts

- Small, random change

- Experimental or speculative change

- Documentation or clarity improvement

- Expanding a feature or functionality

- Changes related to time, dates, or timestamps

- Deploying to production

- Independent change

- Exploration of new technologies or approaches

- Resolution of a complex or hard-to-reproduce issue

- Temporarily masking functionality

- Testing-related changes

- Rapid, impactful changes

- Refactoring code structure

- Making codebase more accessible

- Testing new features or technologies

- Changes to date, time, or scheduling

- Urgent hotfixes

- Urgent production hotfixes

- New feature or enhancement

- Creating or improving environments

- Creation of new components

- Major, transformative change

- Infrastructure changes

- Improving code performance

- Removal of a module, component, or feature

- Significant speed improvement

- Improving code comments or documentation

- Merging branches or connecting code parts