git-commit-push

To safely commit and push git changes, this skill polishes in-scope worktree paths, infers project validation like npm test, runs git diff --check for hygiene, stages intentionally, commits, and pushes only when delivery is proven with final-state evidence.

A git delivery audit inspects and reports worktree status without staging, committing, or pushing. You need it when requesting a review or dry-run to classify changed and untracked paths conservatively before any safe delivery occurs.

Yes, you can inspect changed and untracked paths without pushing by using the audit and status modes, which apply conservative path classification and report worktree hygiene without staging, committing, or pushing any changes.

To resolve a blocked git commit and push decision, the skill continues from a prior GIT_COMMIT_PUSH_DECISION state of blocked or review_needed by inspecting and resolving the named blocker first before attempting delivery again.

Yes, the safe git delivery workflow infers and runs project validation, including npm test when available, before committing to ensure outcomes are validated and only proven changes are pushed with final-state evidence.

Automated git commit and push workflows require explicit audit versus ship mode handling to avoid unsafe delivery, and will not stage, commit, or push changes if validation fails or if git diff --check detects worktree hygiene issues.