PR Branch

Make the actual work's value visible in a screenshot, preserve a useful technical record, and complete the requested PR publication.

Establish the current project and change

Treat invocation as authorization to open/update the matching PR and perform a necessary non-force push without asking again. Honor an explicit narrower request such as description-only or no push. Do not infer permission to commit pending work, change implementation, rewrite history, merge, or start the next workflow stage.

On every invocation or resume, read current project guidance and inspect the checkout, branch, HEAD, working status, remotes, and PR state. Resolve the repository, head owner/branch, and base, including forks and stacked work. Use the user's target; otherwise inspect the matching PR, remote default, upstream, and merge bases. Resolve a consequential ambiguity with one focused question. Do not assume origin, main, or that a supplied PR belongs to the current checkout's branch.