git-commit

To commit changes with an approved draft message, this skill validates your git worktree, stages selected changes, and executes a PowerShell-safe commit using the draft generated by /git-draft-commit. It enforces worktree isolation to prevent accidental commits to protected branches.

A standardized git commit workflow is enforced by requiring a pre-approved draft message before staging and committing. This skill acts as a gatekeeper, ensuring worktree isolation and executing a PowerShell-safe commit followed by a post-commit checklist for traceability.

Yes, a draft message is required before committing. This skill relies on an approved draft produced by the /git-draft-commit workflow to ensure message quality and consistency, preventing unstructured or error-prone commits.

Worktree isolation prevents accidental commits by validating the current git worktree state before staging changes. This ensures you are operating in the correct isolated environment and blocks commits from being applied to protected branches.

Yes, you can execute a PowerShell-safe git commit automatically. The skill handles the command execution safely after staging your selected changes and applying the approved draft message, providing a post-commit checklist to verify the results.

A scripted git commit workflow requires strict adherence to the sequence: you must generate a draft message using /git-draft-commit first. It will not allow direct commit creation without the approved draft, ensuring guardrails but limiting ad-hoc commits.