codex-upcoming-features
SKILL.md
Codex Upcoming Features
Overview
Sync a durable local clone of openai/codex and produce an exhaustive summary of unreleased features and notable improvements since the latest stable (non-prerelease) release tag.
Primary evidence comes from source files that define feature stages and user-facing metadata. Commit/PR analysis is secondary supporting context.
Workflow
- Run
gh auth statusand fail closed if GitHub CLI is not authenticated. - Resolve durable local clone path:
- default:
$CODEX_HOME/repos/<owner>-<repo>(fallback:~/.codex/repos/<owner>-<repo>) - override:
--local-repo <path>
- If clone is missing, clone from
https://github.com/<owner>/<repo>.git. - Sync local clone on every run (
git fetch --tags --prune origin, checkout default branch,git pull --ff-only). - Mine these source files on every run (fail closed if missing):
codex-rs/core/src/features.rscodex-rs/tui/src/chatwidget.rscodex-rs/core/src/codex.rscodex-rs/app-server/src/codex_message_processor.rscodex-rs/app-server-protocol/src/protocol/v2.rscodex-rs/app-server-protocol/schema/json/v2/ExperimentalFeatureListResponse.jsoncodex-rs/app-server/README.mdcodex-rs/tui/src/tooltips.rsannouncement_tip.toml
- Extract source-derived upcoming feature data from
features.rs:
Stage::Experimental(beta/user-facing now)Stage::UnderDevelopment(upcoming but not broadly ready)- include
name,menu_description, andannouncementwhere available
- Extract structured supporting evidence from each other mined source file (UI wiring, app-server mapping, protocol enum/schema, docs contract, tooltip/announcement pipeline).
- Record analyzed commit SHA from synced local clone (
git rev-parse HEAD) and include it in output. - Resolve repo default branch and latest stable release tag (exclude draft/prerelease).
- Compute unreleased range from local git history:
stable_tag..origin/default_branch. - Classify each unreleased commit into one of:
featurenotable_improvement
- Exclude entries that are clearly non-user-impacting (for example docs/chore/test-only).
- Emit an exhaustive report with:
- UTC as-of timestamp
- local repo path used
- analyzed commit SHA
- stable baseline tag and compare link
- source files mined
- source-derived feature list (primary)
- cross-file source evidence (primary)
- per-item PR/commit evidence links
Commands
Run markdown summary (default):
uv run python scripts/summarize_upcoming.py --repo openai/codex
Run JSON output:
uv run python scripts/summarize_upcoming.py --repo openai/codex --output json
Override baseline tag if needed:
uv run python scripts/summarize_upcoming.py --repo openai/codex --base-tag rust-v0.106.0
Override durable local clone path:
uv run python scripts/summarize_upcoming.py --repo openai/codex --local-repo ~/workspace/cache/openai-codex
Output Contract
Always include:
As of (UTC)timestamp- local repo path used for summarization
- analyzed commit SHA
Stable baselinetag- compare URL
- source files mined
- source-derived upcoming feature sections (
beta+underDevelopment) - source-derived cross-file evidence section covering all required files
- exhaustive list of included items
- source links for each item
When there is a conflict between source-derived feature data and commit text, source-derived data wins.
JSON mode returns:
as_of_utcrepolocal_repoanalyzed_commit_shastable_tagcompare_urlsource_files_mined[]source_primary.beta_features[]andsource_primary.under_development_features[]source_primary.supporting_evidence(structured extraction for every required source file)items[]withkind,title,commit_sha,commit_url,pr_number,pr_url(secondary)
Classification Rules
Read references/classification-rules.md before changing filtering behavior. Keep inclusion deterministic and biased toward user-visible changes.
Guardrails
- Do not use stale local commit snapshots; clone if missing and sync (fetch/pull) on every run.
- Fail closed if local repo origin does not match the requested
owner/repo. - Keep release resolution live (GitHub API), source feature extraction local (from mined files), and commit extraction local (synced git history).
- Treat commit messages as supporting evidence only; never treat commits as primary feature truth when source files disagree.
- Do not infer future roadmap from open issues or open PRs in this skill version.
- Fail closed with actionable errors when API/auth/rate-limit calls fail.
Weekly Installs
18
Repository
tkersey/dotfilesGitHub Stars
43
First Seen
Feb 28, 2026
Security Audits
Installed on
gemini-cli18
opencode18
codebuddy18
github-copilot18
codex18
kimi-cli18