Draft PR

Publish the requested work as a draft or work-in-progress PR on the forge that owns the selected remote. Update or squash-merge it only on a corresponding request. Lead the final response with the PR URL and verified state.

Quick Start

1. Preflight Git state, publication remote, forge, exact head and target repositories, provider authentication and authenticated user, base branch, and any existing PR for the current branch.
2. Lock the intended diff. Preserve unrelated worktree changes and meaningful existing PR content.
3. Create a topic branch when on the base branch. Fetch the target remote and rebase only when the topic branch is behind, conflicted, or explicitly needs synchronization.
4. Commit the intended scope, run relevant checks, and push safely. Rewrite only a clearly user-owned topic branch and use --force-with-lease.
5. Write real Markdown to a temporary file, create a draft or work-in-progress PR or update the existing PR through the selected provider adapter, then assign the authenticated user by default.
6. Verify the remote PR fields and report its URL, state, base/head, assignees, results, and any remaining caveat.
7. Merge only on explicit request. Recheck the exact PR and gates, squash-merge through the same adapter, and verify the merged state.

A PR request grants scoped commits and push; do not ask again. If publication is blocked, name the failed command or rule and finish authorized local work.

Do not broaden the task into unrelated refactors, repository cleanup, or rewriting manually maintained PR content.

PR Rules