| name | gstack-upgrade |
| description | Update workflow for this Codex port package. Use when the repo or local skill install should be refreshed and revalidated. |
GStack Upgrade
Use this skill when the local Codex port package should be updated, reinstalled, or checked against upstream changes.
This port was reconciled against garrytan/gstack at commit
94993f74012782fd94416dd44b8314f6363a13a4.
Workflow
- Identify whether the request is about the repo, the local skill install, or both.
- Check the installed Codex version and refresh the current official Codex manual before deciding whether a fallback is still needed:
codex --versionnode "${CODEX_HOME:-$HOME/.codex}/skills/.system/openai-docs/scripts/fetch-codex-manual.mjs"
- Read the manual sections relevant to the port, usually skills, plugins, MCP,
AGENTS.md, sandboxing and approvals, hooks, memories, automations, browser behavior, and local/cloud environments.
- Refresh upstream refs for both
garrytan/gstack and garrytan/gbrain when parity is in scope.
- Port upstream changes into Codex-native skill files instead of copying Claude-specific preambles.
- Reinstall or re-link local skills if needed.
- Run validation and summarize what changed, including the Codex version and any documentation-driven decisions.
Codex Host Audit
When upstream changed since the last port, explicitly decide which parts are:
- clean to port into
skills/, data/, docs/, or tests/
- useful locally but not publishable, such as generated
brain/ corpus pages
- blocked on upstream runtime, database, MCP, browser daemon, or Claude-specific behavior
Prefer current Codex install behavior over older Claude Code fallbacks when Codex has a direct equivalent. Keep fallbacks only for host-variable runtimes such as browser automation, upstream gbrain CLI availability, and remote credentials.
Record Codex documentation refresh results in docs/codex-documentation-refresh.md or the specific runtime/audit doc changed by the upgrade.
Guardrails
- Do not claim an upgrade succeeded without revalidating the install.
- Be explicit about what was updated and what was left alone.
- Do not move baseline source pins forward if only a subset of upstream changes was ported; use per-skill
source_commit metadata instead.
- Do not rely on remembered Codex behavior when the current docs can be checked during the port.
