2026-08-27

⬆️ Upgrade path (existing install)

1. Find your id and scope: claude plugin list — the id is devstride@devstride or ds@devstride; the scope is user unless you installed with --scope project.
2. Run both commands, then restart Claude Code:

   claude plugin marketplace update devstride
   claude plugin update devstride@devstride    # use the id from step 1; add --scope project if needed
   

   The first command alone reports success and changes nothing. After restarting, claude plugin list must show the new version.
3. Check the machine: /devstride:doctor — reports anything missing with its fix (gh signed in with repo + read:org, the DevStride connection, your config). If DevStride is not connected, run /mcp and connect plugin:devstride:devstride.
4. Once per repository: run /devstride:setup docs (scaffolds your documentation skills; migrates the retired release.docsRepo), then /devstride:setup ci, then /devstride:setup. Each proposes diffs and keeps your hand edits. Commit what it writes.
5. Turn on auto-update: set plugin.autoUpdate: true in .claude/ds-config.json (or /plugin → Enable auto-update).

Your skill names and existing config keys are unchanged. Teammates install once per machine (claude plugin install <id>) — the repository's settings.json enables the plugin but does not install it.

🔔 The plugin knows when it is behind (1.2.0)

Every session start compares the running version with the newest release and, only when you are behind, prints the two update commands. Opt in to plugin.autoUpdate and it applies the update and asks you to restart; plugin.pin holds a version without nagging.

📝 Release notes only when you ask (1.0.0)

/devstride:release writes a release note only with --release-notes (true or draft), and only after the deploy is confirmed. Documentation is updated by default through the two skills /devstride:setup docs scaffolds into your repository; no docs suppresses it.

💸 CI runs once (1.1.0)

/devstride:setup ci applies the mechanics — draft gate, per-PR concurrency, a tree-identical skip on production pushes, and a draft-convention check. The release branch is frozen while a release PR is ready, and /devstride:ci-audit reports executed runs and minutes.

🖥️ Local environments and honest verification (1.2.0)

A localEnvironment block in your config describes how to create, seed, migrate and tear down an isolated local instance; setup asks, doctor reports, the hotfix skill uses it. Review verdicts now say "verified X via path Y" and list the paths not tried.

📚 Getting the skills · Configuration reference