菜单
Scan the Codex changelog for new versions, features, and changes. Fetches official release notes, parses them, and generates a structured update report. Use when: checking for new Codex versions, features, or changes since the last known release.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Systematic development workflow: Analyze → Plan → Execute → eLicit → eXamine. Use for ANY development task: features, bug fixes, refactoring, hotfixes. Triggers: "implement", "create", "build", "fix", "add feature", "refactor", "develop". Auto-detects project type (Laravel, Next.js, React, Swift) and loads framework-specific references. Enforces: files <100 lines, interfaces separated, SOLID principles, expert self-review, sniper validation. Modes: --auto (default), --manual, --skip-elicit
Auto-review skill for expert agents. After coding, expert applies elicitation techniques to self-correct before sniper validation. Inspired by BMAD-METHOD. Use when: an expert agent needs to self-review and self-correct code after the Execute phase, before sniper validation.
Use when marking a task as complete, finishing a feature, or claiming a bug is fixed. Ensures functional resolution is verified with evidence before closing. Do NOT use for: lint/type/code-quality validation (use code-quality / sniper AFTER functional verification passes).
Smart conventional commit with security validation, branch flow enforcement, and auto-detection. Use when committing changes, saving work, staging and committing, or choosing a conventional commit message.
Use when committing, branching, opening PRs, or deciding merge strategy. Covers GitHub Flow (default), trunk-based, branch naming conventions, squash vs rebase, branch lifecycle, and protected branch enforcement.
Universal post-commit actions. CHANGELOG update for all repos (git tag is created POST-MERGE, not here — see `commit` command Step 8). Plugin version bumping for marketplace repos. Triggered after any code commit (except wip/amend/undo).
| name | changelog-scan |
| description | Scan the Codex changelog for new versions, features, and changes. Fetches official release notes, parses them, and generates a structured update report. Use when: checking for new Codex versions, features, or changes since the last known release. |
Fetches and analyzes the official Codex release notes to detect new versions and changes. The host platform for this plugin ecosystem is Codex (the openai/codex CLI); this skill tracks its releases.
| Source | Location | Method |
|---|---|---|
| Releases | github.com/openai/codex/releases | gh api repos/openai/codex/releases or browser_fetch |
| Changelog | github.com/openai/codex/blob/main/CHANGELOG.md (raw) | browser_fetch |
| Docs index | github.com/openai/codex docs/ tree | browser_fetch / gh api |
| Config / CLI reference | repo docs/config.md and docs/ CLI pages | browser_fetch |
Prefer the fast-path fetchers (browser_fetch / browser_fetch_batch) — no live browser session — and batch several URLs in one call.
gh api repos/openai/codex/releases (fall back to browser_fetch on the raw CHANGELOG.md). Treat it as a single fetch-parse-persist pass: retrieve the notes, parse each version block, persist the run state, and emit a JSON diff of what is new since the last check.references/templates/changelog-report.md.Parse these patterns from the release notes:
vX.Y.Z / rust-vX.Y.Z and ## X.Y.Z headers — version markers### Breaking Changes — breaking section### New Features / ### Added — features section### Bug Fixes / ### Fixed — fixes sectionLocation: ${CODEX_HOME}/logs/00-changelog/{date}-state.json (CODEX_HOME defaults to ~/.codex). Holds {latest, new_since_last_check, recent_versions} so consecutive scans only report the delta.