codex-changelog
Skill5 starsChanged 48 days agoMITView on GitHub
This skill should be used when the user asks to check for new Codex CLI (codex-cli) releases, "what changed in Codex", "any Codex updates", "check codex releases", "diff the codex version", or wants Codex CLI releases reviewed for changes relevant to THIS repo's Codex bridge. Reads a locally-stored last-checked codex-cli stable version, lists GitHub releases for openai/codex, reports changes relevant to the plugin's Codex integration (bridge argv, sandbox, exec/resume, JSONL output), and offers to advance the stored version.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- zats/skillstheir own version, first seen Jun 30, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- zats/skills★ 19same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository17 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- cc-changelogSkill
- hyper-autoSkill
- hyper-code-reviewSkill
- hyper-docs-loopSkill
- hyper-docs-reviewSkill
- hyper-docs-syncSkill
- hyper-implement-loopSkill
- hyper-implementSkill
- hyper-interviewSkill
- hyper-memorySkill
- hyper-plan-loopSkill
- hyper-plan-reviewSkill
- hyper-planSkill
- hyper-recapSkill
- hyper-researchSkill
- hyper-setupSkill
The file
We split this skill into the rules it gives an agent
6 rules. About 0 are common, 2 are distinctive, and 4 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
4
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 52
Run the local helper — it lists openai/codex releases via gh, finds the latest stable, and prints the notes of every STABLE newer than the …
- Distinctive: line 62
Read the Bash output directly:
- Very specific: line 69
If gh fails (exit 1), fall back to WebFetch https://github.com/openai/codex/releases and read the same stable notes.
- Very specific: line 73
If the output is (up to date — no new stable since <STORED>) (i.e.
- Very specific: line 109
After reporting, offer to update .last-checked-version to LATEST_STABLE (default: yes).
- Distinctive: line 114
Read-only + report only — never edits the bridge as a side effect.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
codex-changelog — Codex CLI release watch (hyperclaude bridge relevance)
Repo-local dev tool (NOT a plugin skill). Compare a stored "last-checked" codex-cli STABLE version against the latest stable release, mine the release notes in between, and report only what touches this repo's Codex bridge — then optionally advance the stored version so the next run diffs from here.
The value is not "summarize Codex releases" — it is mapping generic Codex CLI changes onto the specific surface of the hyperclaude bridge (the only Codex-spawning code in the plugin) and verifying impact against the real bridge files.
Source (differs from cc-changelog)
Codex's CHANGELOG.md only points at GitHub Releases — it is NOT a per-version file.
So the authoritative source is the GitHub Releases of openai/codex, read via gh
(already authed in this repo):
gh release list --repo openai/codex --limit <N>— tags look likerust-v0.142.5(stable) andrust-v0.143.0-alpha.NN(pre-release). The row markedLatestis the current stable.gh release view <tag> --repo openai/codex— the per-release notes.
Step 2's get-releases.mjs helper wraps both calls (list → filter to new stables →
per-new-stable view), so you don't invoke gh by hand in the normal path.
Fallback if gh is unavailable: WebFetch https://github.com/openai/codex/releases.
Track STABLE, note alphas. The plugin runs against the installed stable codex, so
the version diff gates on stable→stable. The alpha stream (-alpha.NN, many per week)
is NOT tracked per-release — but DO surface a one-line "N newer alphas exist (latest
rust-v0.143.0-alpha.NN)" so upcoming changes are visible without firehose noise.
State file
.claude/skills/codex-changelog/.last-checked-version (sibling of this file,
gitignored): a single line with the last-reviewed codex-cli STABLE version, e.g.
0.142.5. It is the diff baseline; it advances only in Step 6.
Procedure
Step 1 — Baseline
The diff baseline is .claude/skills/codex-changelog/.last-checked-version (one stable
X.Y.Z line) — call it STORED. Step 2's helper reads it automatically; you don't Read
it here. If it's missing/empty the helper exits 2 — then ask which stable version to
baseline (or read the installed one via codex --version) and pass it as the argument.
Step 2 — List releases + collect new stable notes
Run the local helper — it lists openai/codex releases via gh, finds the latest
stable, and prints the notes of every STABLE newer than the baseline plus a one-line
alpha-awareness note (it version-compares tags, so skipped numbers are handled; the
per-alpha firehose is collapsed to a count):
node .claude/skills/codex-changelog/get-releases.mjs # reads .last-checked-version
# or with a user-supplied baseline: node .claude/skills/codex-changelog/get-releases.mjs 0.142.5Read the Bash output directly:
LATEST_STABLE=<x.y.z>— the newest stable → this isLATEST_STABLE.ALPHAS=<n> newer[ (latest rust-v…-alpha.NN)]— the alpha-awareness line; surface it verbatim.NOTE: window …— appears only if the 40-release window didn't reachSTORED(older stables may be missing; note it rather than assuming full coverage).- then, per new stable (newest first):
=== <tag> (<name>) ===followed by its notes.
If gh fails (exit 1), fall back to WebFetch https://github.com/openai/codex/releases
and read the same stable notes.
Step 3 — Up-to-date short-circuit
If the output is (up to date — no new stable since <STORED>) (i.e. LATEST_STABLE ==
STORED, no newer stable), report "already current at STORED" — still surface the
ALPHAS= line if newer alphas exist — and STOP. Do not rewrite the state file.
Step 4 — Map the collected stable notes to the bridge
The helper already printed each new stable's notes (Step 2). Classify each relevant item into one of four buckets. Report an item only if it lands on the bridge surface below; never assert impact without checking the anchor file.
Buckets:
- 🔧 Actionable — needs a change in this repo (bridge argv, sandbox handling, parser).
- ✅ Favorable — Codex now does natively what the bridge worked around; no action, note it.
- 🟢 Safe / no-op — plausibly relevant but verified harmless for the bridge.
- ℹ️ Informational — worth knowing, behavior-neutral.
Bridge surface checklist (what to read to confirm impact):
| Surface | What to check | Repo anchors |
| Spawn argv | codex exec --sandbox read-only - (stdin prompt) shape; flag renames/removals/additions | scripts/codex-bridge.mjs, scripts/codex/args.mjs, scripts/codex/codex.mjs |
| Sandbox invariant | --sandbox read-only (fresh) + -c sandbox_mode=read-only (resume) semantics; whether resume inherits sandbox | scripts/codex/*.mjs, CLAUDE.md (Sandbox invariant) |
| exec / resume | codex exec + codex exec resume behavior; thread/session semantics; the removed native exec review subcommand | scripts/codex/resume.mjs, docs/decisions.md |
| Output parsing | stdout JSON/JSONL shape + fields the bridge parses (thread-id, token counts) | scripts/codex/codex.mjs (parseCodexJsonl) |
| Config overrides | -c key=value behavior | scripts/codex/args.mjs |
| Min version / prereqs | codex-cli minimum-version requirement | CLAUDE.md, scripts/setup-doctor.mjs |
For any flagged-but-uncertain item, deepen (read the anchor file / the full release note) before concluding.
Step 5 — Report
Lead with a one-line TL;DR answering "does anything need action?". Then the four buckets
(omit empty ones or say "none"), plus the alpha-awareness line. Cite repo files as
clickable [path](path) links. Keep it tight — a bridge-maintainer triage, not a
release-notes reprint.
Step 6 — Advance the baseline
After reporting, offer to update .last-checked-version to LATEST_STABLE (default:
yes). On confirmation, overwrite the file with LATEST_STABLE + newline. Skip the bump
if the user wants to keep the current baseline for re-review. Never bump before reporting.
Notes
- Read-only + report only — never edits the bridge as a side effect. Any actionable finding is handed back to the user to act on (e.g. via hyper-plan).
- Companion to the
cc-changelogskill (sibling under.claude/skills/) — same shape, different source (GitHub Releases viaghvs a rawCHANGELOG.md).
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

