yeetlisted

# GitHub Publish Changes ## Overview Use this skill only when the user explicitly wants the full publish flow from the local checkout: branch setup if needed, staging, commit, push, and opening a pull request. This workflow is hybrid: - Use local `git` for branch creation, staging, commit, and push. - Prefer the GitHub app from this plugin for pull request creation after the branch is on the remote. - Use `gh` as a fallback for current-branch PR discovery, auth checks, or PR creation when the connector path cannot infer the repository or head branch cleanly. ## Prerequisites - Require GitHub CLI `gh`. Check `gh --version`. If missing, ask the user to install `gh` and stop. - Require authenticated `gh` session. Run `gh auth status`. If not authenticated, ask the user to run `gh auth login` (and re-run `gh auth status`) before continuing. - Require a local git repository with a clean understanding of which changes belong in the PR. ## Naming conventions - Branch: `codex/{description}` when starting from main/master/default. - Commit: `{description}` (terse). - PR title: `[codex] {description}` summarizing the full diff. ## Workflow 1. Confirm intended scope. - Run `git status -sb` and inspect the diff before staging. - If the working tree contains unrelated changes, do not default to `git add -A`. Ask the user which files belong in the PR. 2. Determine the branch strategy. - If on `main`, `master`, or another default branch, create `codex/{description}`. -