Discover and use relevant installed skills for publishing pull requests and communicating the change.

Work scope:

{{ context.work }}

Inspect the prepared worktree, current branch and any associated pull request.

Push the intended local commits. Update the existing open PR, or create one against the repository’s intended target branch. Describe the complete change, its relationship to the work scope and the verification performed. When the commit messages record review decisions, state each decision and its reason in the description. Keep an existing `Open items` section, and remove an item only when the published change resolves it.

Use ticket references only when the work scope identifies an existing ticket. When it does, write `Closes #N` in the description if the change completes that ticket, and `Part of #N` if it only advances it.

If the associated PR is already merged and the branch contains follow up changes, open a new PR.

Confirm the PR URL from the remote. If publication fails, inspect the current remote state before retrying. Preserve local work and avoid creating duplicate PRs.

This step owns publication. Leave implementation files and tracker records unchanged. Later steps handle PR feedback, CI and conflicts. The caller owns any tracker updates.

Return `publication_summary` with the PR URL, confirmed remote state and published commits.