Agent skill

Release Tracking Update

by FlorianBruniaux in FlorianBruniaux/claude-code-ultimate-guide

Updates a guide repository's release tracking: checks for new Codex releases, edits the tracking files and landing page, and optionally bumps the guide version and changelog.

CC-BY-SA-4.0Auto-check passedDevelopment

Install Release Tracking Update

skills CLI
$ npx skills add FlorianBruniaux/claude-code-ultimate-guide --skill source-command-update-infos-release -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install FlorianBruniaux/claude-code-ultimate-guide source-command-update-infos-release --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/FlorianBruniaux/claude-code-ultimate-guide.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/source-command-update-infos-release .claude/skills/source-command-update-infos-release && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
source-command-update-infos-release
GitHub stars
6.1k
Token cost
~1.7k tokens
SKILL.md length
328 words
Files
1
Skills in repo
14
Repo updated
First seen
Licence
CC-BY-SA-4.0

At a glance

Updates a guide repository's release tracking: checks for new Codex releases, edits the tracking files and landing page, and optionally bumps the guide version and changelog.

  • Works in 7 steps: Check for New Codex Releases → Update Codex Releases Tracking → Guide Version Bump (if requested) → …
  • Recording a new tool release in the guide's tracking files and landing page
  • SKILL.md covers Command Template, Usage, Workflow Steps and Error Handling, plus 3 more sections
  • Calls git; reaches cc.bruniaux.com and florianbruniaux.github.io

What it does

This skill wraps the `/update-infos-release` command from a Claude Code guide repository. Run on its own it only updates release tracking; with `patch` or `minor` it also bumps the guide version. It starts by running `./scripts/update-cc-releases.sh` and stops if no new versions turn up. Otherwise it reads the release notes, picks the version, date and two to four highlights, and updates the machine-readable YAML, the Markdown release guide and the landing page badge and releases section, keeping the top five.

Condensing rules mark major features with a star, put breaking changes in their own array, reduce bug fixes to one line and skip internal or SDK changes unless they break something. A requested version bump reads the VERSION file and syncs the README, cheatsheet, main guide and reference YAML by script. Then the skill adds a CHANGELOG.md entry, adds an RSS entry only for releases with a starred feature, breaking changes or at least three highlights, and checks synchronization with `./scripts/check-landing-sync.sh`.

When your agent uses it

  • Recording a new tool release in the guide's tracking files and landing page
  • Bumping the guide's patch or minor version along with a release update
  • Checking that the landing page and guide files stay in sync after a release

Example prompts

  • “Run update-infos-release and tell me if there are new releases to record.”
  • “Update the release tracking and bump the guide patch version.”
  • “Update the releases with a minor version bump and add the changelog entry.”

Requirements

  • A checkout of the guide repository with the update-cc-releases.sh and check-landing-sync.sh scripts

Workflow steps

7 steps, taken from the step headings in SKILL.md.

  1. Check for New Codex Releases
  2. Update Codex Releases Tracking
  3. Guide Version Bump (if requested)
  4. Update CHANGELOG.md
  5. Verify Synchronization
  6. Commit and Push
  7. Summary Output

What it can do on your machine

Read from SKILL.md and the folder at commit 585c203. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • git

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    Hosts in commands or code, which the agent is likely to contact:

    • cc.bruniaux.com
    • florianbruniaux.github.io

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Release Tracking Update loads about 1.7k tokens when it runs. Until then it costs about 25 tokens; SKILL.md has 328 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~25
When it runs · the whole SKILL.md, loaded when a task matches
~1.7k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from FlorianBruniaux/claude-code-ultimate-guide at commit 585c203, republished under its CC-BY-SA-4.0 licence (© FlorianBruniaux). 328 words, ~1,746 tokens.

Download SKILL.mdSave it as .claude/skills/source-command-update-infos-release/SKILL.md (or your agent's skills folder).
name
source-command-update-infos-release
description
Update Codex releases tracking (guide + landing + version bump)

source-command-update-infos-release

Use this skill when the user asks to run the migrated source command update-infos-release.

Command Template

Release Management Workflow

Automate Codex releases tracking and guide version management.

Usage

/update-infos-release          # Update CC releases only (no guide version bump)
/update-infos-release patch    # Update CC + bump guide patch (3.9.11 → 3.9.12)
/update-infos-release minor    # Update CC + bump guide minor (3.9.11 → 3.10.0)
/update-infos-release major    # Update CC + bump guide major (3.9.11 → 4.0.0)

Workflow Steps

1. Check for New Codex Releases
bash
./scripts/update-cc-releases.sh

If new versions detected, continue. Otherwise, stop.

2. Update Codex Releases Tracking

Files to update:

  • machine-readable/Codex-releases.yaml
  • guide/Codex-releases.md
  • Codex-ultimate-guide-landing/index.html (badge + section)

Process:

  1. Read latest release notes from the command output
  2. Extract version, date, and highlights (2-4 key features max)
  3. Update YAML with condensed highlights
  4. Update Markdown with expanded details
  5. Update landing badge version
  6. If major features, update landing #releases section (keep top 5)

Condensation rules for YAML:

  • ⭐ Major features get star emoji
  • Breaking changes → breaking: array
  • Bug fixes → single line
  • 2-4 highlights max (focus on user-facing changes)
  • Skip internal/SDK changes unless breaking
3. Guide Version Bump (if requested)

If bump-type specified:

bash
# Read current version
cat VERSION

# Bump version
# patch: 3.9.11 → 3.9.12
# minor: 3.9.11 → 3.10.0
# major: 3.9.11 → 4.0.0

# Update VERSION file
echo "X.Y.Z" > VERSION

# Sync version across docs
./scripts/sync-version.sh

Files synced by script:

  • README.md
  • guide/cheatsheet.md
  • guide/ultimate-guide.md
  • machine-readable/reference.yaml
4. Update CHANGELOG.md

Add entry:

markdown
## [X.Y.Z] - YYYY-MM-DD

### Documentation

- **Codex Releases**: Updated tracking to vA.B.C
  - [Feature 1]
  - [Feature 2]
  - [Feature 3]

[If guide version bump:]
### Version Bump

- Bumped guide version: [old] → [new]
- Reason: [major features added / significant updates / breaking changes in CC]
4.5. Add RSS Entry (for notable CC releases)

Add an entry to src/data/rss-entries.ts in the landing repo only if at least one of:

  • Release has ⭐ feature(s)
  • Release has breaking changes
  • Release has ≥3 highlights

If none of these → skip (patch/bugfix-only releases don't need an RSS entry).

Entry format:

typescript
{
  type: 'guide_release',
  title: 'Codex vX.Y.Z',
  date: 'Mon DD, YYYY',
  description: '[1-2 sentences: main feature(s), plain text no HTML]',
  link: 'https://cc.bruniaux.com/releases/#vX.Y.Z',
},

Prepend at the top of the rssEntries array.

5. Verify Synchronization
bash
./scripts/check-landing-sync.sh

Expected output:

✅ Version guide:    X.Y.Z
✅ Templates:        N
✅ Quiz questions:   N
✅ Guide lines:      N
✅ Codex:      vA.B.C

If mismatches, fix before committing.

6. Commit and Push

Two repositories to update:

Guide Repository
bash
cd /Users/florianbruniaux/Sites/perso/Codex-ultimate-guide

git add \
  VERSION \
  CHANGELOG.md \
  README.md \
  guide/cheatsheet.md \
  guide/ultimate-guide.md \
  guide/Codex-releases.md \
  machine-readable/reference.yaml \
  machine-readable/Codex-releases.yaml

# If version bump:
git commit -m "release: vX.Y.Z

- Update Codex releases tracking (vOLD → vNEW)
- [Bump type]: vOLD_GUIDE → vNEW_GUIDE
- Update CHANGELOG with release details

Co-Authored-By: Codex Sonnet 4.5 <noreply@anthropic.com>"

# If CC releases only:
git commit -m "docs: update Codex releases to vA.B.C

- Update latest tracked version: vOLD → vNEW
- Add vNEW highlights: [feature1], [feature2], [feature3]
- [Any breaking changes or fixes]
- Update dates: YYYY-MM-DD

Co-Authored-By: Codex Sonnet 4.5 <noreply@anthropic.com>"

git push
Landing Repository
bash
cd /Users/florianbruniaux/Sites/perso/Codex-ultimate-guide-landing

git add index.html

git commit -m "chore: sync with guide vX.Y.Z

- Update Codex version badge: vOLD → vNEW
[If releases section updated:]
- Update releases timeline with vNEW features
- Maintain top 5 notable releases
- Maintain landing/guide synchronization

Co-Authored-By: Codex Sonnet 4.5 <noreply@anthropic.com>"

git push
7. Summary Output

Display to user:

✅ Release Update Complete

Guide Repository:
- Version: [old] → [new]
- Codex: vA.B.C
- Commit: [hash]
- Files: [count] updated

Landing Repository:
- Codex badge: vA.B.C
- Commit: [hash]
- Files: [count] updated

Synchronization: ✅ All synced

Next Steps:
1. Verify GitHub Pages deployment: https://florianbruniaux.github.io/Codex-ultimate-guide-landing/
2. Check version badge displays correctly
3. [If major release] Update social media / announcements

Error Handling

If no new Codex versions:

ℹ️ No new Codex releases detected.
Current tracked: vX.Y.Z
Latest available: vX.Y.Z

Aborting. Nothing to update.

If sync check fails:

❌ Synchronization check failed:
[List mismatches]

Please fix manually before committing.
Run: ./scripts/check-landing-sync.sh

If git operations fail:

❌ Git operation failed: [error]

Manual intervention required.
Check: git status

Examples

Example 1: Update CC releases only
User: /update-infos-release

Output:
✅ New Codex release detected: v2.1.15
   Date: 2026-01-22
   Highlights:
   - New feature X
   - Fix for Y
   - Improvement Z

Updating tracking files...
✅ YAML updated
✅ Markdown updated
✅ Landing badge updated

Verifying sync... ✅ All synced

Committing changes...
✅ Guide: commit abc1234
✅ Landing: commit def5678

✅ Release Update Complete
Example 2: Update CC + minor bump
User: /update-infos-release minor

Output:
✅ New Codex release detected: v2.2.0
   Major release with significant features

Current guide version: 3.9.11
Bumping to: 3.10.0 (minor)

Updating files...
✅ Codex tracking updated
✅ Guide version bumped
✅ CHANGELOG updated
✅ All docs synced

Verifying sync... ✅ All synced

Committing changes...
✅ Guide: commit abc1234 (8 files)
✅ Landing: commit def5678 (1 file)

✅ Release Update Complete (v3.10.0)

Implementation Notes

  • Atomicity: If any step fails, rollback git changes (git reset --hard)
  • Idempotency: Can be run multiple times safely
  • Validation: Always verify sync before committing
  • User confirmation: Ask before version bump if ambiguous
  • Smart defaults: No bump = CC update only
  • /version - Check current versions (guide + CC)
  • /changelog - View recent CHANGELOG entries
  • /sync - Run sync check without updates

© FlorianBruniaux, CC-BY-SA-4.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in .agents/skills/source-command-update-infos-release of FlorianBruniaux/claude-code-ultimate-guide.

Open the folder on GitHubat commit 585c203

Compare with similar skills

Release Tracking Update next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Release Tracking Update compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Release Tracking Update this skillFlorianBruniaux/claude-code-ultimate-guide6.1k—~1.7kAutomated safety check: PassCC-BY-SA-4.0
Simple Englishmoeru-ai/airi50k2 repos~4.6kAutomated safety check: PassMIT
Ccb GitHubSeemSeam/claude_codex_bridge3.6k—~4.9kAutomated safety check: PassCustom licence
Golang Documentationunxed/f42413 repos~3.5kAutomated safety check: PassMIT
Simple Englishropensci/ckanr1043 repos~2kAutomated safety check: PassMIT
Opik Documentation Patternscomet-ml/opik22k—~1.3kAutomated safety check: PassApache-2.0

Similar skills

  • Simple English

    moeru-ai/airi

    Write or rewrite technical text with the rules of ASD-STE100 Simplified Technical English so it is clear, unambiguous, and free of AI slop.

    50k GitHub starsUsed in 2 repos~4.6k tokens
    DevelopmentAuto-check passed
  • Ccb GitHub

    SeemSeam/claude_codex_bridge

    Maintain this CCB project's GitHub-facing release and npm publication surface.

    3.6k GitHub stars~4.9k tokensUpdated today
    DevelopmentAuto-check passed
  • Comprehensive documentation guide for Golang projects, covering godoc comments, README, CONTRIBUTING, CHANGELOG, Go Playground, Example tests, API docs, and llms.txt.

    241 GitHub starsUsed in 3 repos~3.5k tokens
    DevelopmentAuto-check passed
  • Simple English

    ropensci/ckanr

    Write or rewrite text in plain, layman-readable English in the spirit of ASD-STE100 Simplified Technical English: short sentences, active voice, simple tenses, one word one meaning, condition before…

    104 GitHub starsUsed in 3 repos~2k tokens
    DevelopmentAuto-check passed
  • Rules for writing PR descriptions, changelog entries and feature documentation in the Opik repository, including the exact headings that CI requires.

    22k GitHub stars~1.3k tokensUpdated today
    DevelopmentAuto-check passed
  • Release

    jrswab/axe

    Prepare code for release (version bumps, changelog, README updates) and create an annotated tag to trigger the GoReleaser workflow.

    895 GitHub stars~1.4k tokensUpdated 3 days ago
    DevelopmentAuto-check passed

More from FlorianBruniaux/claude-code-ultimate-guide

All 14 skills in this repo
  • Changelog Social Recap

    FlorianBruniaux/claude-code-ultimate-guide

    Turns CHANGELOG.md entries for a release or a week into LinkedIn, Twitter/X, newsletter and Slack posts in French and English.

    6.1k GitHub stars~1.8k tokensUpdated yesterday
    Auto-check: notes
  • Codex Skill Self-Assessment

    FlorianBruniaux/claude-code-ultimate-guide

    Runs an interactive quiz in a quick or comprehensive mode, scores your skill level by topic and generates a personalized learning path with practice projects.

    6.1k GitHub stars~2.3k tokensUpdated yesterday
    Auto-check passed
  • Whitepaper Bare Section Prose Filler

    FlorianBruniaux/claude-code-ultimate-guide

    Adds two to four sentences of intro prose before each bare heading in the French and English whitepapers, splitting the work across nine parallel agents.

    6.1k GitHub stars~1.5k tokensUpdated yesterday
    Auto-check passed
  • Audit Whitepapers

    FlorianBruniaux/claude-code-ultimate-guide

    Audits version freshness, French and English parity and metadata of whitepapers and recap cards in the claude-code-ultimate-guide repo, with optional fix suggestions.

    6.1k GitHub stars~3.8k tokensUpdated yesterday
    Auto-check passed
  • Methodology Advisor

    FlorianBruniaux/claude-code-ultimate-guide

    Reads a codebase silently, asks only what it cannot infer, and recommends one AI-assisted development methodology stack with a contextual quick start.

    6.1k GitHub stars~1.9k tokensUpdated yesterday
    Auto-check passed
  • Guide and Landing Sync Check

    FlorianBruniaux/claude-code-ultimate-guide

    Check guide/landing synchronization status

    6.1k GitHub stars~692 tokensUpdated yesterday
    Auto-check passed

Categories

Questions about Release Tracking Update

What does Release Tracking Update do?

Updates a guide repository's release tracking: checks for new Codex releases, edits the tracking files and landing page, and optionally bumps the guide version and changelog. This skill wraps the `/update-infos-release` command from a Claude Code guide repository. Run on its own it only updates release tracking; with `patch` or `minor` it also bumps the guide version.

When should I use Release Tracking Update?

Release Tracking Update fits situations like: recording a new tool release in the guide's tracking files and landing page; bumping the guide's patch or minor version along with a release update; checking that the landing page and guide files stay in sync after a release.

How do I install Release Tracking Update in Claude Code?

Run `npx skills add FlorianBruniaux/claude-code-ultimate-guide --skill source-command-update-infos-release -a claude-code`. Or copy the skill folder (.agents/skills/source-command-update-infos-release in FlorianBruniaux/claude-code-ultimate-guide) into .claude/skills/source-command-update-infos-release in your project. Claude Code loads it when a task matches its description.

How do I install Release Tracking Update in Codex?

Run `npx skills add FlorianBruniaux/claude-code-ultimate-guide --skill source-command-update-infos-release -a codex`. Or copy the skill folder (.agents/skills/source-command-update-infos-release in FlorianBruniaux/claude-code-ultimate-guide) into .agents/skills/source-command-update-infos-release in your project. Codex loads it when a task matches its description.

Can I use Release Tracking Update in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add FlorianBruniaux/claude-code-ultimate-guide --skill source-command-update-infos-release -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/source-command-update-infos-release, .gemini/skills/source-command-update-infos-release, .github/skills/source-command-update-infos-release and .opencode/skills/source-command-update-infos-release in your project.

What does Release Tracking Update need to run?

Going by SKILL.md and its folder, Release Tracking Update needs the command-line tools its instructions call (git). Our summary lists: A checkout of the guide repository with the update-cc-releases.sh and check-landing-sync.sh scripts.

Does Release Tracking Update access the network?

SKILL.md names 2 domains. In commands or code: cc.bruniaux.com and florianbruniaux.github.io; the agent is likely to contact these when it follows the instructions. This is read from the text; nothing was executed.

Is Release Tracking Update safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Release Tracking Update use?

Release Tracking Update is published under the CC-BY-SA-4.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Release Tracking Update use?

About 1.7k tokens (SKILL.md is roughly 7k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Release Tracking Update?

Skills that share tags, products or a category with Release Tracking Update: Simple English (moeru-ai/airi, 50k stars), Ccb GitHub (SeemSeam/claude_codex_bridge, 3.6k stars), Golang Documentation (unxed/f4, 241 stars) and Simple English (ropensci/ckanr, 104 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Release Tracking Update?

FlorianBruniaux (a GitHub user) maintains it in FlorianBruniaux/claude-code-ultimate-guide, which has 6,126 GitHub stars. The repository holds 14 skills in this directory. The repository was last updated on October 7, 2026.

Source: FlorianBruniaux/claude-code-ultimate-guide on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.