Updates Claude Code CLI release tracking within the Claude Code Ultimate Guide, following its documented workflows. It can also handle an explicitly requested guide version bump and report changes, verification results, and unresolved checks.
Update the Claude Code Ultimate Guide's CLI release tracking and optionally bump the guide version. Use for 'mets à jour le suivi des releases Claude Code dans le guide', 'synchronise la dernière version CLI avec le landing', or the update-infos-release command. Not for Codex CLI releases, checking installed software updates, writing a generic changelog, or publishing without authorization.
Review the instructions the agent will receive before you install.
Canonical skill: .claude/skills/source-command-update-infos-release/. The Codex copy is generated by scripts/sync-release-tracking-skill.py; edit the canonical source and regenerate it.
.claude/commands/update-infos-release.md from the guide root in full, together with docs/workflows/releases-tracking.md and docs/workflows/landing-sync.md. Those files own the workflow and RSS source split. Preserve the product name Claude Code and actual repository paths on either host. Done when the current workflow and permitted edits are identified.No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Evaluate Claude Code agents, skills, and commands with weighted quality criteria. Get scores, readiness grades, template comparisons, and practical improvement suggestions in Markdown or JSON reports to guide reviews before release.
Assess a codebase across seven areas, including exposed credentials, security, dependencies, structure, and tests. Receive category scores, findings tied to file locations, and a prioritized improvement plan with smaller tasks that can be completed quickly.
Measure code patterns such as casts to any or disabled lint rules, then run repeated, targeted edits. Keep changes that improve the chosen metric, revert unsuccessful changes, and track results for each improvement loop.
Generate several separate solutions, compare them against criteria fixed in advance, and verify the selected result through executable checks or an independent reviewer. Keep a proof log documenting candidates, evidence, failures, and remaining limits.
Monitor a live application after deployment and compare it with a saved baseline, a record of its earlier state. Check page responses, loading times, and new errors, flag persistent changes, and produce a per-page health report.
Rebuild project context after clearing a conversation or returning to work. Review recent Git history, uncommitted changes, and TODO markers to get a structured summary of project status and suggested next steps.