Skip to content
Skills Library
Programming · Automation

update

/update

Regency update. Bring a project to the installed regency: read its stamp, plan every operation the newer version needs (replace untouched scaffold files, put the new text beside edited ones, create, rename, move, delete, rewrite what regency owns, then stamp), apply the whole plan on the Regent's one yes in a clean git tree, and check. Never touches the project's own prose, its acts or .scope/. Use for /regency:update, when a command says the project needs an update first, or 'update this project to the new regency', 'migrate the guidelines'.

Repository
regency ↗
Licence
MIT
Last repository change
06.11.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 06.11.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Regency update. Bring a project to the installed regency: read its stamp, plan every operation the newer version needs (replace untouched scaffold files, put the new text beside edited ones, create, rename, move, delete, rewrite what regency owns, then stamp), apply the whole plan on the Regent's one yes in a clean git tree, and check. Never touches the project's own prose, its acts or .scope/. Use for /regency:update, when a command says the project needs an update first, or 'update this project to the new regency', 'migrate the guidelines'.

Triggers from the description

update this project to the new regencymigrate the guidelines

Arguments

/update [plan | check]
Original author description

Regency update. Bring a project to the installed regency: read its stamp, plan every operation the newer version needs (replace untouched scaffold files, put the new text beside edited ones, create, rename, move, delete, rewrite what regency owns, then stamp), apply the whole plan on the Regent's one yes in a clean git tree, and check. Never touches the project's own prose, its acts or .scope/. Use for /regency:update, when a command says the project needs an update first, or 'update this project to the new regency', 'migrate the guidelines'.

How it works

  1. Procedure
  2. After merging by hand
  3. plan and check alone
  4. Boundaries
Original SKILL.md headings · 56 lines, 474 words
SKILL.md preview
---
name: update
description: "Regency update. Bring a project to the installed regency: read its stamp, plan every operation the newer version needs (replace untouched scaffold files, put the new text beside edited ones, create, rename, move, delete, rewrite what regency owns, then stamp), apply the whole plan on the Regent's one yes in a clean git tree, and check. Never touches the project's own prose, its acts or .scope/. Use for /regency:update, when a command says the project needs an update first, or 'update this project to the new regency', 'migrate the guidelines'."
argument-hint: "[plan | check]"
disable-model-invocation: true
---

# update — fit the project to the installed regency

> **Root.** This file is `skills/update/SKILL.md`; the regency root is two directories above it, and
> `library/…`, `scripts/…` paths are relative to it. Read `library/conventions.md` once per session and
> `library/migrations/README.md` before the first update of a session.

The engine is `scripts/migrate.py`. It decides what changes; this playbook only runs it, shows it and
asks once. Run every command from inside the project.

## Procedure

1. **Gate.** `python <regency>/scripts/migrate.py gate`.
   - exit 2 (the project is newer): stop. Say so in its words and give the two plugin commands from
     `library/migrations/README.md` §3. Never move a project back.
   - exit 0 (agree): say "the project fits regency `<version>`", run `check`, and stop.
   - exit 1 (behind or unstamped): go on.
2. **Plan.** `python <regency>/scripts/migrate.py plan`. Show it as it prints: one numbered line per
   operation, the refused ones, the plan id. Group nothing and drop nothing.
3. **Clean tree.** `apply` refuses uncommitted changes and a folder that is not a git repository. If the
   tree is dirty, say which files, and offer `/regency:arrange-cycle-commit` first; do not stash or commit
   the Regent's work yourself.
4. **One yes.** One pop-up: "Apply plan `<id>` — `<n>` operations (replace, beside, create, rename, delete,
   rewrite, stamp)?", options *Apply* and *Do not apply*. Read the free text too. No yes, no apply.
5. **Apply.** `python <regency>/scripts/migrate.py apply --yes <id>`. A refusal (the plan changed, the tree
   got dirty) means: plan again and ask again.
6. **Check.** `python <regency>/scripts/migrate.py check` must exit 0.
7. **Ledger.** One item, state `review`: `regency update <from> -> <to>`, `where` the changed files and
   the plan id, `next` "merge the `.template` files by hand, then `migrate.py merged`" when there are any.
8. **Report** in the shape below. Commit nothing; offer `/regency:arrange-cycle-commit`.

```text
regency update 2.6 -> 2.10 · plan UPD-1a2b3c4d · 9/9 applied (100%)
Replaced  7 untouched files     Beside  1 (.plan/README.md.template — merge by hand)
Renamed   0  Deleted 0  Rewritten 0  Created 0  Refused 0
Stamp     .guidelines/.shortcuts/regency.json -> 2.10   check: fits
```

## After merging by hand

Merge each `.template` into its file in the project's own language (regency's sources are English, the
project's prose is not), delete the `.template`, then record it:
`python <regency>/scripts/migrate.py merged <path>...` (guidelines-relative, or the `.template` path). The stamp
keeps that text's fingerprint, so `check` passes and the plan stops putting it beside the file; a newer
template goes beside it again. A `.template` deleted without the record comes back on the next plan.

## `plan` and `check` alone

`/regency:update:plan` runs steps 1–2 and stops: a dry run. `/regency:update:check` runs `check` and reports
its line.

## Boundaries

Never edits a file by hand to "help" the plan, never applies without the Regent's yes to that plan id,
never rewrites the project's own prose, an act or `.scope/`, never downloads anything, never commits.

Versions

RepositoryScoreLicence
This page · Trevojan/regency100MIT
nimbalyst/nimbalyst100MIT
nimbalyst/nimbalyst100MIT
nimbalyst/nimbalyst100MIT
jl-cmd-projects/claude-dev-env100MIT
abatyuk/okf100MIT
tony/skills100MIT
crisandrews/clawcode100MIT
nextwork-projects/ai-video-editor-cooked100MIT

Database snapshot: 13.11.2026 · package version dbcca9c9cc71 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 90init
    Regency init. Scaffold the .guidelines/ structure (sources, decisions, plan, orders, constraints, changelog, shortcuts, history), a root CLAUDE.md and README into a project, from the bundled template. Names every path before creating it and never overwrites. Use for…
  • 100regency
    Regency, the Regent's harness built on Claude Code, and the entry point for /regency and every /regency:* command. AA works as a PO/DV/QA/DA team and the Regent decides at the review packet; the rules travel as files and scripts: five inference engines, the Scribe, Orders and…
  • 86upgrade
    Move a repository that was set up with an older discipline version to the current one - read the changelog, apply its migration notes, add new template files, update the gate's pinned version and the profile's version stamp, and verify. Use when the user asks to upgrade, or when…
  • 100update-kit
    Update the kit's own files to the latest release without touching the creator's files. Use when the creator says "update the kit", "get the latest version", "is there a new version", "check for updates", "upgrade the kit" or "apply the update".
  • 90sb:update
    This skill should be used when the user runs `/sb:update` or asks to update Silver Bullet — checks GitHub for the latest release, shows the changelog since the installed version, and installs the update after confirmation.
  • 90update-xperience
    Updates an Xperience by Kentico project to a newer version. Use when the user wants to update or upgrade their Xperience by Kentico project, apply a hotfix, or move to a newer refresh.

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.