commit

To prevent accidental commits to protected branches, this Skill enforces branch safety by stopping commits on main or master and prompting to create context-named feature, fix, or refactor branches before staging and pushing changes.

You can automate generating conventional commit messages by applying this Skill to your local repository; it analyzes staged changes and automatically formats semantic commit messages, stages the changes, commits, and pushes to origin.

Yes, this git commit automation works inside linked worktrees by automatically detecting the worktree context and avoiding creating or switching branches when operating within a worktree, ensuring safe version control operations.

The best way to safely push semantic commits without force pushing is using automated branch protection rules that generate conventional commit messages, stage changes, commit, and push to origin while explicitly avoiding force pushes.

To create a feature branch from main and push a fix in one step, apply this Skill to your local repository; it detects if you are on main, creates a context-named branch, stages changes, generates a semantic commit, and pushes to origin.

Conventional commits may fail in a git worktree if branch switching is attempted incorrectly; this Skill detects linked worktrees and avoids creating or switching branches to ensure version control operations remain safe and auditable.