ptoas-publish-pr

To publish a GitHub pull request with only specific worktree files, stage only the intended local changes, validate them, commit, and push to a fork remote to open a focused draft PR. This prevents unrelated worktree files from being included in the pull request.

Creating a pull request from a fork without untracked files requires scoped staging, where only intended changes are committed to a feature branch and pushed to the fork remote. The worktree safety mechanism ensures unrelated files remain excluded from the final GitHub pull request.

Yes, you need GitHub CLI to create a draft pull request against an upstream repository. Authenticated GitHub credentials and correctly configured origin and upstream remotes are also required to push changes from your fork and open the PR against the canonical repository.

Scoped git staging works by selectively adding only the intended modified files to the index, creating a feature branch when needed, and committing those specific changes. This workflow isolates targeted modifications from unrelated worktree files before pushing to a remote fork.

Your pull request validation may fail because quick_validate.py detected issues with affected skills before pushing to your fork. The repository safety checks also inspect branches, worktree state, remotes, and GitHub CLI authentication, halting the process if prerequisites are not met.