Some checks failed
Tests / PR mergeability (push) Successful in 1m37s
Tests / Base branch health (push) Successful in 11s
Tests / Detect test scope (push) Successful in 17s
Tests / lint-tests (push) Failing after 2m16s
Tests / plugin-validate (push) Successful in 1m6s
Tests / test (ubuntu-latest, 24, shard 1/3) (push) Failing after 25s
Tests / test (ubuntu-latest, 24, shard 2/3) (push) Failing after 20s
Tests / test (ubuntu-latest, 24, shard 3/3) (push) Failing after 20s
Tests / test (ubuntu-latest, 24) (push) Failing after 19s
Tests / test (inert CI) (push) Has been skipped
Tests / QA loop walk (smell ratchet) (push) Failing after 19s
Tests / Coverage gate (merged shards) (push) Has been skipped
Tests / Publish emitted-baseline artifact (push) Has been skipped
Dismiss Unauthorized PR Approvals / dismiss-unauthorized-approval (push) Successful in 9s
Close Draft PRs (sweep) / Sweep open draft PRs (push) Successful in 8s
Tests / conformance test (macos-latest, 24) (push) Has been cancelled
Tests / conformance test (windows-latest, 24, shard 1/3) (push) Has been cancelled
Tests / conformance test (windows-latest, 24, shard 2/3) (push) Has been cancelled
Tests / conformance test (windows-latest, 24, shard 3/3) (push) Has been cancelled
Tests / Required tests (push) Has been cancelled
The fork lives on the golem15 Gitea forge, not GitHub. Package identity now parses either host and derives in-place raw URLs for Gitea; the identity-drift lint accepts the new host; README drops GitHub-only badges and the npm quickstart in favour of the checkout installer.
1.8 KiB
1.8 KiB
Manual Update (Non-npm Install)
Use this procedure when npx @golem15/msd-core@latest is unavailable — e.g. during a publish outage or if you are working directly from the source repo.
Prerequisites
- Node.js installed
- This repo cloned locally (
git clone https://git.golem15.com/golem15/msd-core)
Steps
# 1. Pull latest code
git pull --rebase origin main
# 2. Build the hooks dist (required — hooks/dist/ is generated, not checked in as source)
node scripts/build-hooks.js
# 3. Run the installer directly
node bin/install.js --claude --global
# 4. Clear the update cache so the statusline indicator resets
rm -f ~/.cache/msd/msd-update-check.json
Step 5 — Restart your runtime to pick up the new commands and agents.
Runtime flags
Replace --claude with the flag for your runtime:
| Runtime | Flag |
|---|---|
| Claude Code | --claude |
| OpenCode | --opencode |
| Kilo | --kilo |
| Codex | --codex |
| Copilot | --copilot |
| Cursor | --cursor |
| Windsurf | --windsurf |
| Augment | --augment |
| All runtimes | --all |
Use --local instead of --global for a project-scoped install.
What the installer replaces
The installer performs a clean wipe-and-replace of MSD-managed directories only:
~/.claude/msd-core/— workflows, references, templates~/.claude/commands/msd/— slash commands~/.claude/agents/msd-*.md— MSD agents~/.claude/hooks/dist/— compiled hooks
What is preserved:
- Custom agents not prefixed with
msd- - Custom commands outside
commands/msd/ - Your
CLAUDE.mdfiles - Custom hooks
Locally modified MSD files are automatically backed up to msd-local-patches/ before the install. Run /msd-update --reapply after updating to merge your modifications back in.