review-fix-commit

To automate code review and commit preparation, you inspect staged and unstaged git diffs to detect dead code, naming inconsistencies, and type errors, apply immediate fixes, execute full test suites, and generate descriptive commit messages following project conventions.

The best way to ensure a feature branch is ready for a clean commit is to enforce an end-to-end workflow: review all code changes, remediate discovered critical and minor issues, execute the project test suites, and push with a descriptive commit message.

Yes, you can use an automated workflow to review both frontend and backend code changes. The process applies to feature branches and bugfix workflows across both domains, checking for security issues, misconfigurations, and type errors before finalizing the commit.

Yes, the code review and commit process runs full test suites after applying fixes. It ensures that mocks align with implementations and re-runs the project test suites after remediating issues to verify the changes before generating the final commit.

A key limitation of automated code review and commit preparation is that it avoids large-scale refactors. It focuses on applying immediate fixes for critical issues and minor adjustments like naming and dead code removal, ensuring changes remain suitable for a clean commit.