Windows Git Ops

Overview

Use this skill when the task involves Git commands on Windows PowerShell. It prevents shell-specific mistakes, keeps Git operations auditable, and favors simple non-interactive command sequences over clever chained commands.

Hard Rules

• Assume the shell is PowerShell unless the environment clearly says otherwise.
• Do not use bash-only chaining or redirection syntax such as &&, ||, <<EOF, or other POSIX-only forms.
• Prefer one command per shell invocation for Git operations. Do not compress unrelated steps into a single shell string.
• Use non-interactive Git commands only. Avoid commands that open editors or interactive prompts.
• Before mutating Git state, inspect it with targeted commands such as git status --short, git branch --show-current, git diff --name-only, or git diff --cached --name-only.
• Stage only intended files. Never use broad staging when the change set should stay narrow.
• When committing from a dirty worktree, confirm the staged set matches the intended change before git commit.
• Do not revert, reset, or discard user changes unless the user explicitly asked for it.
• When creating a branch in Codex, use the required codex/ prefix.

PowerShell-Safe Patterns