FerroxLabs Routes to the update workflow which handles:
- Version detection (local vs global installation)
- npm version checking
- Changelog fetching and display
- User confirmation with clean install warning
- Update execution and cache clearing
- Restart reminder
Ferrox Update
You want the latest Ferrox, with the changelog shown before anything changes
Ferrox Update by FerroxLabs · 201691f
npx skillmds@latest add ferroxlabs/ferrox-update File contents
---name: ferrox-updatedescription: You want the latest Ferrox, with the changelog shown before anything changes---<objective>Check for Ferrox updates, install if available, and display what changed.Routes to the update workflow which handles:- Version detection (local vs global installation)- npm version checking- Changelog fetching and display- User confirmation with clean install warning- Update execution and cache clearing- Restart reminder</objective><execution_context>@~/.claude/ferrox-core/workflows/update.md</execution_context><flags>- **--sync**: Sync managed Ferrox skills across runtime roots so multi-runtime users stay aligned after an update. Runs the sync-skills workflow (--from, --to, --dry-run, --apply flags supported).- **--reapply**: Reapply local modifications after a Ferrox update. Uses three-way comparison (pristine baseline, user-modified backup, newly installed version) to merge user customizations back. Runs the reapply-patches workflow.- **--next** (alias **--rc**): Target the `@next` RC dist-tag instead of `@latest` so you can install or refresh a release candidate (e.g. `1.4.0-rc.1`) through the normal update flow — scope/runtime detection, changelog preview, custom-file backup, and cache clearing all still apply. Omitting it keeps targeting `@latest` (no change). See ADR #660 for the RC channel.- **(no flag)**: Standard update — check for new version, show changelog, install.</flags><process>Parse the first token of $ARGUMENTS:- If it is `--sync`: strip the flag, execute the sync-skills workflow (passing remaining args for --from/--to/--dry-run/--apply).- If it is `--reapply`: strip the flag, execute the reapply-patches workflow.- Otherwise (including `--next` / `--rc`): execute the update workflow end-to-end, passing `$ARGUMENTS` through so the workflow's parse_update_channel step can select the release channel.</process><execution_context_extended>@~/.claude/ferrox-core/workflows/sync-skills.md@~/.claude/ferrox-core/workflows/reapply-patches.md</execution_context_extended>
ferroxlabs/ferrox-factory/tree/main/skills/ferrox-update commit 201691f698
Frequently asked questions
Run npx skillmds@latest add ferroxlabs/ferrox-update in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.
You want the latest Ferrox, with the changelog shown before anything changes It is listed under Coding & Dev Tools on SkillMD.
This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.
This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.
Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.
FerroxLabs (@ferroxlabs) published this skill. Their other Agent Skills are listed on their SkillMD profile.