publish-changes

name	publish-changes
description	Commit local changes, push the branch, and open or update a GitHub pull request.
when_to_use	Use when the user asks to commit, push, publish, open a PR, or prepare changes for review.
triggers	["open pr","publish changes","push branch","create pull request","draft pr"]

Publish Changes

Use this skill when local changes need to become a GitHub branch or PR.

Before committing:

• Inspect git status --short and git diff --stat.
• Review relevant diffs before staging so unrelated user changes are not included accidentally.
• Verify the current branch name and upstream with git branch --show-current and git status -sb.

Commit intentionally:

• Stage only the intended files.
• Use a terse commit message that names the functional change.
• Do not add AI-provider attribution, generated markers, badges, or co-author trailers.

Publish:

• Push the branch with git push -u origin <branch> when no upstream exists.
• Use gh pr create --draft unless the user asks for a ready PR or an existing PR should be updated.
• Keep PR descriptions high-level and functional: what changed and why. Do not include command logs, test plans, file tours, or implementation narration unless it is part of the public contract.

If the checkout contains unrelated changes, leave them untouched and state what was intentionally included.