Git Workflow

Use native Git UI, diff/review tools, and shell commands for ordinary operations. Follow the user's repository/branch workflow; do not introduce PRs, commits, pushes, or a new branch merely because a generic example uses them.

Inspect status and preserve unrelated/uncommitted work. Destructive reset/restore/clean, history rewrites, tag moves, and checkpoint commits require explicit approval of their scope. Never force-push a shared branch or rewrite a published tag. Use non-interactive commands and disable pagers.

Before an authorized push, or after a non-interactive Git authentication failure, run the bundled Git auth checker in preview mode (node <this-skill>/scripts/check-git-auth.cjs --repository-root <repo> --user <account>). A repository owner may be an organization; do not infer the login from it. Use --hostname explicitly for GitHub Enterprise; other HTTPS providers are not automatically treated as GitHub. This environment's observed credential.interactive=never is not a universal host claim. Preview verifies selected-token identity, repository read access, and actual credential-helper execution without printing tokens or changing global account selection. Branch push policies remain separately verified. Apply needs explicit consent; it validates a prepared helper and atomically replaces local config with rollback on a failed post-apply probe.

Load only the applicable recovery, authentication, or release procedure in execution details. Commands there illustrate effects, not permission to run them. Prefer a scoped, reversible action; when unsure, inspect or dry-run and report the decision needed. A fetch does not merge; a requested fast-forward must refuse divergence.

Return the actual command result and resulting branch/worktree state. Do not equate an exit code with broader integration or test success.

Apply the shared artifact storage contract to project deliverables: check that final files and dependencies are discoverable and not ignored. Repository presence, staging, a local commit, a push, and a verified remote commit are separate states. Report the observed state; storage requirements alone do not authorize commits or pushes.