codex-changelog
Codex Changelog
Goal
Resolve the installed Codex CLI and Codex App versions and return two sections:
Codex CLI: the matching GitHub release changelog fromopenai/codex/releasesCodex App: the matching desktop-app changelog fromhttps://developers.openai.com/codex/changelog
Trigger rules
- Use when the user asks for Codex version, release notes, or changelog details for the CLI, app, or both.
- Prefer this skill for installed-version changelog lookups instead of ad-hoc browsing.
- Always fetch Codex CLI notes from GitHub Releases, even though the OpenAI changelog page also lists CLI entries.
- If no installed CLI or app version can be resolved, report the failure and provide the nearest fallback tags or app versions.
Workflow
- Run
python3 scripts/print_codex_changelog.py. - Share the printed changelog with the user in two sections:
Codex CLIandCodex App.
More from alemar11/skills
postgres
Connect to Postgres databases, run SQL and diagnostics, inspect schemas and migrations, review query performance, and use common PostGIS or pgvector patterns.
47learn
Capture durable corrections or preferences and write confirmed learnings only to AGENTS.md. Use when the user sets lasting guidance.
27ask-questions-if-underspecified
Clarify requirements before implementing when a request is underspecified or the user asks for clarification.
24skill-audit
Audit installed or user-specified Codex skills, plugins, or bundled plugin skills using project history, repo evidence, memory, sessions, and current context to plan updates, additions, merges, or disables. Use when a user asks how their installed Codex surfaces are performing, wants a one-by-one refinement roadmap, asks to audit a skill, a plugin, or a bundled plugin skill, or wants evidence-based recommendations before changing those surfaces.
13github
Handle repo-scoped GitHub work plus authenticated-user star and star-list workflows through one repo-owned skill covering triage, reviews, CI, releases, and PR publish or lifecycle flows, with `yeet` reserved for full local-worktree publish.
12commit
Create a well-formed git commit from current changes using session history for rationale and summary; prefer explicit pathspec staging and, in monorepos, default to one subproject per commit unless the user asks for a cross-cutting commit. Use when asked to commit, prepare a commit message, or finalize staged work.
7