commit

Automate git commits by using a workflow that stages specified files, performs a code review, generates a standardized commit message, and executes a git push. This enforces best practices while handling session-modified files or all uncommitted changes.

Standardized git commit messages are enforced by generating a specific format like [type]: [description] during the commit process. This ensures consistency across project history by automating the message creation based on the staged changes.

Automated code review during a git commit works by integrating with a code review skill to identify issues before staging and pushing. If the review fails, robust error handling stops the commit process to prevent bad code from entering version control.

Yes, selective file staging allows you to commit specific files, all uncommitted changes, or session-modified files. This flexibility ensures you only version control the exact modifications you want to push to the repository.

Git push conflicts are managed through robust error handling built into the workflow automation. When push conflicts occur, the process halts to prevent overwrites, ensuring you can manually resolve version control discrepancies before retrying.

No, manual git add is unnecessary because the automated workflow handles staging internally. It identifies session-modified files or specific files based on your input and stages them automatically before generating the commit message.