Skip to content

refactor: rename gpt-5-4-prompting skill to codex-prompting#307

Open
tonyyunyang wants to merge 1 commit intoopenai:mainfrom
tonyyunyang:rename-prompting-skill-model-agnostic
Open

refactor: rename gpt-5-4-prompting skill to codex-prompting#307
tonyyunyang wants to merge 1 commit intoopenai:mainfrom
tonyyunyang:rename-prompting-skill-model-agnostic

Conversation

@tonyyunyang
Copy link
Copy Markdown

Summary

  • Rename the gpt-5-4-prompting skill to codex-prompting so the label doesn't go stale as GPT iterates. The skill is really about prompting Codex (the runtime), not a specific GPT generation, and Codex already routes to whatever model the user has configured.
  • Drop "GPT-5.4" mentions from the skill body and reference files. Update cross-references in agents/codex-rescue.md and skills/codex-cli-runtime/SKILL.md.
  • Replace example gpt-5.4-mini strings in the README and the agent's model-passthrough rule with a <your-model> placeholder, since the actual model selection flows through ~/.codex/config.toml and --model.
  • Update assertions in tests/commands.test.mjs to match.

Net-zero diff: 8 files, 21 insertions, 21 deletions. Folder rename detected by git (history preserved).

Test plan

  • node --test tests/commands.test.mjs — all 8 assertions pass on the new branch
  • No remaining gpt-5-4 / GPT-5.4 / gpt-5.4-mini strings in user-facing .md/.mjs/.json/.toml (verified via grep)
  • Pre-existing failures in runtime.test.mjs and state.test.mjs confirmed unrelated — same 4 failures appear on baseline main when this branch's changes are stashed

Notes

  • tests/fake-codex-fixture.mjs still has gpt-5.4 as a mock-server fallback. It's internal test infrastructure (not user-facing, not asserted on); left untouched to keep the diff minimal.
  • The skill name has to be static — Claude Code resolves it from frontmatter at load time and can't reflect runtime config dynamically. Making it model-agnostic is the closest practical equivalent to "tied to whatever model the user has configured."

The skill label baked in a specific GPT generation, so it goes stale
whenever the underlying model iterates. Codex itself already routes to
whatever model the user has configured in ~/.codex/config.toml, so the
skill name shouldn't promise a specific generation.

- Rename folder + SKILL.md frontmatter: gpt-5-4-prompting -> codex-prompting
- Drop "GPT-5.4" mentions from skill body and reference files
- Update cross-references in agents/codex-rescue.md and codex-cli-runtime
- Replace gpt-5.4-mini examples in README with <your-model> placeholder
- Update test assertions in commands.test.mjs to match
@tonyyunyang tonyyunyang requested a review from a team May 8, 2026 12:55
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant