GitHub Publisher
Overview
Publish this repository carefully through GitHub while keeping user intent, credentials, proxy settings, and unrelated local changes visible. This skill is procedural: do not commit, push, tag, or create releases unless the user explicitly asks for that action.
Workflow
- Read
references/publish-workflow.md before preparing a publish operation.
- Inspect
git status --short and relevant diffs before staging anything.
- Run tests and
python3 tools/validate_skills.py.
- Confirm the intended scope when there are unrelated or surprising changes.
- Stage only the approved files.
- Commit only after the user asks for a commit.
- Push only after the user asks for a push.
- Read
references/troubleshooting.md when auth, proxy, remote, or push errors appear.
Safety Rules
- Do not silently stage unrelated files.
- Do not print, store, or ask the user to paste GitHub tokens into chat.
- Do not bypass network, GitHub, branch protection, or authentication restrictions.
- Do not use destructive git commands unless the user explicitly requests them.
- Prefer
gh auth login and gh auth setup-git over manual token handling.
References
references/publish-workflow.md: status, diff, test, commit, remote, auth, push, and release-note sequence.references/troubleshooting.md: proxy, auth, remote, branch, and network failure checks.
1---2name: github-publisher3description: Guide safe GitHub publishing for this codex-skills repository. Use when Codex needs to prepare commits, push branches, configure or inspect remotes, handle gh authentication, account for proxy settings, draft release notes, troubleshoot push/auth/network failures, or publish repository changes without silently including unrelated files or exposing credentials.4---56# GitHub Publisher78## Overview910Publish this repository carefully through GitHub while keeping user intent, credentials, proxy settings, and unrelated local changes visible. This skill is procedural: do not commit, push, tag, or create releases unless the user explicitly asks for that action.1112## Workflow13141. Read `references/publish-workflow.md` before preparing a publish operation.152. Inspect `git status --short` and relevant diffs before staging anything.163. Run tests and `python3 tools/validate_skills.py`.174. Confirm the intended scope when there are unrelated or surprising changes.185. Stage only the approved files.196. Commit only after the user asks for a commit.207. Push only after the user asks for a push.218. Read `references/troubleshooting.md` when auth, proxy, remote, or push errors appear.2223## Safety Rules2425- Do not silently stage unrelated files.26- Do not print, store, or ask the user to paste GitHub tokens into chat.27- Do not bypass network, GitHub, branch protection, or authentication restrictions.28- Do not use destructive git commands unless the user explicitly requests them.29- Prefer `gh auth login` and `gh auth setup-git` over manual token handling.3031## References3233- `references/publish-workflow.md`: status, diff, test, commit, remote, auth, push, and release-note sequence.34- `references/troubleshooting.md`: proxy, auth, remote, branch, and network failure checks.
CoUse-123