migrate
Bring a project to the shape of a release that changed the shape of files — a dry run first, the migration on the principal's word, the threads' origins judged, then /save
Install
npx skills add https://github.com/pche-broken-artist/forge-of-thought/tree/main/.claude/skills/migrate
claude plugin marketplace add https://llmmart.ai/marketplace.json && claude plugin install pche-broken-artist-forge-of-thought@llmmart
git clone https://github.com/pche-broken-artist/forge-of-thought.git
The skills CLI installs just this skill, for any of its supported agents. Claude Code installs the whole pche-broken-artist/forge-of-thought collection as a plugin from our marketplace. Git is the plain clone.
Skill manifest
The door to scripts/forge-migrate.py (SOL.0800, POS.1740): the
script does every deterministic step and is described in full by its
help header; this command adds what needs judgement and runs
nothing without the principal's word. A migration runs once per
project, on one clone, on main; everyone else pulls (the
refusals and the way back are the script's).
- Infer the project from context (
$0may be a slug;forgeis the engine's own project; if ambiguous, ask). Run the dry run,python scripts/forge-migrate.py <slug>, and show its print as it came: the marks of the shape, the steps that would run and what each would change. A project already in shape ends here. - On the principal's word, and only then, run
python scripts/forge-migrate.py <slug> --apply. The script commits nothing. - Judge what the script printed for the principal: the origins it
guessed for the threads it cut (
threads/THR.NNNN.md, the fieldorigin), the text after the last thread that was not a thread, the Waiting lines without an ID. The origins are a walkthrough (CLAUDE.md, Working methods): one table of Claude's judgement from the texts, the principal correcting what is wrong, written into the thread files at the round's end; what is not a thread goes where it belongs, usually a record of the intent's history. - Make the ledger,
python scripts/forge-ledger.py <slug>, and propose/save <slug>; the migrated shape reaches the remote by that save. Should anything be wrong, the way back is the script's, as its header says; the tag before the migration is POS.1740's, taken through/save <slug> --tag <name>before--apply.
Files (forge-of-thought)
-
SKILL.md 1.9 KB
--- description: Bring a project to the shape of a release that changed the shape of files — a dry run first, the migration on the principal's word, the threads' origins judged, then /save argument-hint: "[project-slug]" disable-model-invocation: true --- The door to `scripts/forge-migrate.py` (SOL.0800, POS.1740): the script does every deterministic step and is described in full by its help header; this command adds what needs judgement and runs nothing without the principal's word. A migration runs once per project, on one clone, on `main`; everyone else pulls (the refusals and the way back are the script's). 1. Infer the project from context (`$0` may be a slug; `forge` is the engine's own project; if ambiguous, ask). Run the dry run, `python scripts/forge-migrate.py <slug>`, and show its print as it came: the marks of the shape, the steps that would run and what each would change. A project already in shape ends here. 2. On the principal's word, and only then, run `python scripts/forge-migrate.py <slug> --apply`. The script commits nothing. 3. Judge what the script printed for the principal: the origins it guessed for the threads it cut (`threads/THR.NNNN.md`, the field `origin`), the text after the last thread that was not a thread, the Waiting lines without an ID. The origins are a walkthrough (CLAUDE.md, Working methods): one table of Claude's judgement from the texts, the principal correcting what is wrong, written into the thread files at the round's end; what is not a thread goes where it belongs, usually a record of the intent's history. 4. Make the ledger, `python scripts/forge-ledger.py <slug>`, and propose `/save <slug>`; the migrated shape reaches the remote by that save. Should anything be wrong, the way back is the script's, as its header says; the tag before the migration is POS.1740's, taken through `/save <slug> --tag <name>` before `--apply`.
Comments (0)
Sign in to join the conversation.
Reviews (0)
No reviews yet.
No comments yet.