commit-push

This skill automates git commit and push operations by batching staged changes per component, enforcing conventional commit messages, validating branches, and conditionally pushing changes only upon explicit user request.

To prevent sensitive files like .env from being committed to git, this skill performs pre-flight checks during staging to detect and block sensitive files, ensuring they are excluded before batching commits by component type.

You can batch git commits by component scope automatically using this skill, which groups staged files based on their file paths and assigns the correct component scope to each generated conventional commit message.

Yes, this git commit skill enforces English strictly for all code comments and commit messages. It also applies specific language requirements for internal and public documentation to ensure standardized repository communication.

Yes, you can separate git commit and push actions. This skill conditionally pushes changes to the remote repository only upon explicit user instruction, allowing you to safely review batched commits before executing the push.

Automating git push without pre-flight branch validation risks committing to protected branches or including too many staged files. This skill mitigates these limitations by strictly enforcing branch validation and staged file count checks before batching.