github-delivery

name	github-delivery
description	Use when a verified work item explicitly requires Git branch creation, intentional commits, non-force push, pull-request handoff, or authorized artifact delivery. Do not use outside a Git repository or to publish a formal Release without explicit authorization.

GitHub Delivery

Deliver only the verified, authorized scope.

1. Require explicit user authorization for the requested Git action. Read the sidecar task/track evidence, repository instructions, and references/git-delivery-policy.md.
2. Confirm Git repository, current branch, clean understanding of unrelated changes, remote, authentication, and requested destination.
3. Run fresh required verification and inspect the final diff before staging.
4. Stage only intended paths; create a descriptive commit without rewriting unrelated history.
5. Push the branch without force only when a remote exists and authentication succeeds.
6. Create or update a PR only when requested; include task evidence, risks, platform gaps, and release impact.
7. Record commit SHA, branch, remote, push/PR result, and any artifact destination in the selected sidecar task Result. This Skill never creates a worktree or chooses a task automatically.

Do not change remotes or credentials to make push succeed. Git push, artifact upload, draft Release, formal Release, and registry publication are separate authorizations.