Files

Jakub Zych a9a7a328e6 refactor: hard-fork GSD -> MSD (Make Software Done)

Mechanical rename produced by scripts/msd-rename.cjs: gsd/Gsd/GSD -> msd/Msd/MSD
across contents and paths, upstream package/repo coordinates -> @golem15/msd-core
and golem15com/msd-core. Deep links into upstream history, sibling upstream
packages, the GSD-2 import feature, CHANGELOG.md and .changeset/ are kept as-is.

Hand edits on top: MSD block-letter banner and logos, LICENSE copyright line,
package/plugin identity, regenerated lockfile, install-tree fixtures, derived
registries and benchmark baseline; migration checksum baseline re-locked
(MSD keeps its own install state, so no install had applied the old sums);
sort-order and regex-escaped expectations in tests adjusted.

2026-10-06 01:47:40 +02:00

1.1 KiB

Raw Blame History

Issue tracker: GitHub

Issues for this repo live in GitHub Issues at golem15com/msd-core.

Auth

Use the configured GitHub CLI session for this checkout. Do not require a repo-local .envrc before running gh.

Conventions

Create: gh issue create --repo golem15com/msd-core --title "..." --body "..."
Read: gh issue view <number> --repo golem15com/msd-core --comments
List: gh issue list --repo golem15com/msd-core --state open --json number,title,labels --jq '...'
Comment: gh issue comment <number> --repo golem15com/msd-core --body "..."
Label: gh issue edit <number> --repo golem15com/msd-core --add-label "..." --remove-label "..."
Close: gh issue close <number> --repo golem15com/msd-core --comment "..."

Always pass --repo golem15com/msd-core explicitly — the local clone has multiple remotes and gh may resolve to the wrong one.

When a skill says "publish to the issue tracker"

Create a GitHub issue at golem15com/msd-core.

When a skill says "fetch the relevant ticket"

Run gh issue view <number> --repo golem15com/msd-core --comments.

1.1 KiB Raw Blame History