commit-and-push

To automate git commit and push, this Skill stages explicitly selected files, generates formatted commit messages based on recent log patterns, and pushes changes to your remote repository. It enforces atomic commits to ensure a clean and traceable version history.

Keeping git commit messages consistent is achieved by generating messages based on observed log patterns. This Skill analyzes your recent commit history to maintain a uniform style, ensuring every commit follows the established formatting conventions automatically.

Guided staging prevents sensitive information in git commits by requiring explicit file selection. This Skill ensures only relevant, designated files are staged, stopping accidental inclusion of unrelated changes or sensitive data before pushing to the remote repository.

You can create separate atomic commits for distinct code changes by staging files individually. This Skill enforces commit atomicity by encouraging distinct commits for each logical change, then pushing all updates to your Git repository branch.

You need to explicitly stage relevant files before committing. This Skill requires guided staging to prevent accidental inclusion of unrelated files, ensuring only intended changes are committed and pushed to maintain a clean version history.

This git workflow requires explicit staging to enforce commit atomicity and prevent sensitive information from entering version control. By avoiding automatic mass staging, it ensures a clean, traceable history with only relevant, deliberately selected code changes.