source-command-update-infos-release

Automate Codex release tracking and guide version bumps across YAML and markdown.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/srednoff888-art/4 --skill source-command-update-infos-release
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: source-command-update-infos-release
Source: https://github.com/srednoff888-art/4/tree/main/.agents/skills/source-command-update-infos-release
Command: npx skills add https://github.com/srednoff888-art/4 --skill source-command-update-infos-release

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill automates the tedious process of tracking Codex releases and updating related documentation and landing pages, reducing manual effort and ensuring consistency.

Core Features & Use Cases

  • Automated release detection and tracking across machine-readable YAML and guide docs
  • Guide version bump support (patch/minor/major) with optional updates to the landing page badge
  • End-to-end workflow with scripts to run release updates and synchronization checks

Quick Start

Run /update-infos-release to refresh Codex release tracking and, if desired, bump the guide version.

Frequently Asked Questions about source-command-update-infos-release

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate Codex release tracking across YAML and markdown files?

Codex release tracking can be automated by running an update command that detects new releases and applies changes across YAML, markdown, and landing badges. It replaces manual version checks and keeps documentation synchronized.

How do I bump guide versions for patch, minor, and major releases?

Guide version bumps are handled by selecting patch, minor, or major update options during the release command. The process optionally updates the landing page badge to reflect the new version.

What's the best way to keep documentation versions synchronized with releases?

Keeping documentation synchronized is best done using scripts that verify consistency after applying updates. The workflow detects releases, updates YAML and markdown, and verifies all version references match.

Does this release tracking workflow support machine-readable YAML files?

Yes, the workflow explicitly supports updating machine-readable YAML files alongside guide markdown and landing badges. It ensures all machine-readable metadata stays current with the latest Codex releases.

Can I verify documentation synchronization after applying a version bump?

Yes, synchronization can be verified by running the provided scripts in the scripts directory. These scripts check that YAML files, markdown guides, and landing badges all reflect the same release version.