Enable Remote Publication
UTILITY SKILL. INVOKES: git, gh, GitHub app tools. FOR SINGLE OPERATIONS: remote auth/readiness checks only.
Read remote publication flow before choosing a push target or verification command.
USE FOR:
- Auth or remote setup that blocks another skill from publishing.
- Verifying an exact shell push,
gh PR mutation, or app review/comment path.
- Explaining the next safe setup step when the target cannot yet be verified.
DO NOT USE FOR:
- Creating, updating, or monitoring PRs once remote publication already works.
- Committing local changes, branch review, CI repair, or Git tutorials.
- Mutating branches, PRs, comments, or reviews during auth setup.
Examples
why can't Codex push this branch?set up github auth for Codex
Workflow
- Capture
original_task and any caller-supplied push target.
- Inspect remotes, upstream, push overrides,
gh auth status, and credential or SSH state.
- Preserve exact caller targets; do not fall back to
origin or upstream unless the reference says it is intended.
- Identify required capabilities: shell push,
gh PR mutation, approval review, review comments, or app-only mutation.
- Verify non-destructively with the matching dry-run or read-only probe. For app-only paths with no non-mutating probe, say "ready to attempt", not verified.
- If setup is missing, give exact user-run commands. Do not run auth bootstrap unless asked.
- Report status, verification command, auth path, and a one-line
continue prompt when original_task exists.
Troubleshooting
If the same check fails twice, explain the blocker instead of retrying. If git only failed because a pager is missing, retry with git --no-pager.
1---2name: enable-remote-publication3description: Use when Codex must set up or verify GitHub remote publication after a blocked workflow, including git push auth, exact PR-head targets, force-push repair, gh PR mutation auth, app review/comment readiness, or why can't Codex push. Do not use for normal PR creation after auth works, CI monitoring, branch review, generic git help, or local-only commits.4---56# Enable Remote Publication78**UTILITY SKILL. INVOKES:** `git`, `gh`, GitHub app tools. **FOR SINGLE OPERATIONS:** remote auth/readiness checks only.910Read [remote publication flow](references/remote-publication-flow.md) before choosing a push target or verification command.1112## USE FOR:1314- Auth or remote setup that blocks another skill from publishing.15- Verifying an exact shell push, `gh` PR mutation, or app review/comment path.16- Explaining the next safe setup step when the target cannot yet be verified.1718## DO NOT USE FOR:1920- Creating, updating, or monitoring PRs once remote publication already works.21- Committing local changes, branch review, CI repair, or Git tutorials.22- Mutating branches, PRs, comments, or reviews during auth setup.2324## Examples2526- `why can't Codex push this branch?`27- `set up github auth for Codex`2829## Workflow30311. Capture `original_task` and any caller-supplied push target.322. Inspect remotes, upstream, push overrides, `gh auth status`, and credential or SSH state.333. Preserve exact caller targets; do not fall back to `origin` or upstream unless the reference says it is intended.344. Identify required capabilities: shell push, `gh` PR mutation, approval review, review comments, or app-only mutation.355. Verify non-destructively with the matching dry-run or read-only probe. For app-only paths with no non-mutating probe, say "ready to attempt", not verified.366. If setup is missing, give exact user-run commands. Do not run auth bootstrap unless asked.377. Report status, verification command, auth path, and a one-line `continue` prompt when `original_task` exists.3839## Troubleshooting4041If the same check fails twice, explain the blocker instead of retrying. If git only failed because a pager is missing, retry with `git --no-pager`.
willakins