# Crew Update

> Check for a newer version, update, report what changed, then prompt /clear to reload.

- **Type:** Skill
- **Install:** `agentstack add skill-crewforth-crewforth-crew-update`
- **Verified:** Yes — security-reviewed for prompt injection and unsafe behavior
- **Seller:** [crewforth](https://agentstack.voostack.com/s/crewforth)
- **Installs:** 0
- **Category:** [AI & ML](https://agentstack.voostack.com/c/ai-and-ml)
- **Latest version:** 0.1.0
- **License:** MIT
- **Upstream author:** [crewforth](https://github.com/crewforth)
- **Source:** https://github.com/crewforth/crewforth/tree/main/kit/skills/crew-update
- **Website:** https://crewforth.com/

## Install

```sh
agentstack add skill-crewforth-crewforth-crew-update
```

Requires the [AgentStack CLI](https://agentstack.voostack.com/docs/cli). Works with Claude Code, Cursor, and any MCP-compatible agent.

## About

# /crew-update
Bring the Crewforth install up to the latest published version:
1. **Detect install type.** If `.claude/VERSION` exists → a full install (steps below). If Crewforth runs as a
   **plugin** (no `.claude/VERSION`), it updates through the plugin system: run
   `claude plugin update crewforth@crewforth`, tell the user it applies when they restart Claude Code, and stop here.
2. **Current version:** read `.claude/VERSION`.
3. **Latest version:** `npm view crewforth version` (needs network). If it can't be reached,
   say so and stop — don't guess.
4. **Compare.** Already on the latest → report "up to date (vX)" and stop. Otherwise show **old → new**.
5. **Before:** run `bash .claude/eval/update-guard.sh pre`. It records what is on disk (in `.claude/.state/`, nothing
   else) and prints one of three verdicts:
   - `clean` → nothing to report, go on.
   - `UNCOMMITTED:` with the changed paths in `.claude/` and `CLAUDE.md` → show the user that list and **ask** —
     with your question tool — whether to go ahead (the update rewrites Crewforth-owned files under `.claude/`), commit
     or stash first, or stop. Continue only on their yes.
   - `NOT IN GIT:` (a private install gitignores `.claude/` and `CLAUDE.md`, so edits there cannot be detected) →
     pass its two lines to the user and go on; there is nothing to commit.
6. **Update** — this rewrites Crewforth-owned files under `.claude/` (your `./CLAUDE.md` and project skills are
   preserved). **Show this plan first, then run:** `npx --yes crewforth@latest update --here --yes`.
   Two DIFFERENT `--yes` flags, both required for a non-interactive run: the one **before** the package name is
   **npx's own** — it auto-confirms npx's `Ok to proceed?` install prompt, which reads the real TTY and IGNORES piped
   input, so without it the command hangs before Crewforth even starts. The `--here --yes` **after** the package go to
   the updater (`--here` = apply on the current branch, `--yes` = accept the smart defaults). Together they let it run
   to completion instead of blocking on a prompt your shell can't answer.
   If you'd rather review each handover decision yourself, tell the user to run `npx crewforth@latest update`
   (no flags) in **their own terminal**, where both the npx and the interactive prompts work.
7. **After:** run `bash .claude/eval/update-guard.sh post` and show the user its lists — added, changed, moved,
   removed.
8. **Verify:** run `/crew-doctor` (or `bash .claude/eval/doctor.sh`) so a bad/partial update surfaces immediately.
   If the updater's or doctor's output contains a line starting with ⭐, pass it to the user verbatim as the LAST
   line of your summary — it prints once per Crewforth version, and it is meant for the user, not for you.
9. **Report** old → new + the headline changes. Take them from `.claude/.state/whats-new.md` — the updater writes
   there the installed package's own CHANGELOG sections between the old and the new version. Do not fetch release
   notes from the network. No file → say no release notes were included.
10. **Reload (manual — a command can't do it itself):** the discipline in the running session is still the OLD one.
   Tell the user to run **`/clear`** (or quit and relaunch Claude Code): a new session loads the updated
   `.claude/DISCIPLINE.md`.

## Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

- **Author:** [crewforth](https://github.com/crewforth)
- **Source:** [crewforth/crewforth](https://github.com/crewforth/crewforth)
- **License:** MIT
- **Homepage:** https://crewforth.com/

Install and usage instructions live in the source repository linked above.

## Pricing

- **Free** — Free

## Security capabilities

Automated source analysis of v0.1.0 — what this tool can access:

- **Network access:** no
- **Filesystem access:** no
- **Shell / process execution:** no
- **Environment & secrets:** no
- **Dynamic code execution:** no

*"Yes" means the capability is present in the source — more access means more to trust, not that it is unsafe.*


## Versions

- **0.1.0** — security scan: passed — Imported from the upstream source.

## Links

- Listing page: https://agentstack.voostack.com/l/skill-crewforth-crewforth-crew-update
- Seller: https://agentstack.voostack.com/s/crewforth
- Browse the marketplace: https://agentstack.voostack.com/browse

---
Listed on AgentStack — the marketplace for AI agent skills and MCP servers. Every listing is security-reviewed. Creators keep 70%.
