Skip to content

Rename skill to spacecraft-steelbore-standard — v1.49 - #42

Closed
UnbreakableMJ wants to merge 1 commit into
feat/std-v1.48-mvp-rowfrom
feat/skill-rename-steelbore-standard
Closed

Rename skill to spacecraft-steelbore-standard — v1.49#42
UnbreakableMJ wants to merge 1 commit into
feat/std-v1.48-mvp-rowfrom
feat/skill-rename-steelbore-standard

Conversation

@UnbreakableMJ

Copy link
Copy Markdown
Contributor

Stacked on #41 (retargets to main when #41 squash-merges and its branch is deleted). Standard-side counterpart: Spacecraft-Software/Standard#28, same version and date.

Renames spacecraft-standard-constitutionspacecraft-steelbore-standard, so the skill id carries the document's canonical name (skill ids are §2.2 functional identifiers).

  • Directory + frontmatter name:; masthead → v1.49 / 2026-08-16; description unchanged at 988/1000.
  • README.md §2 catalogue + nix build example (flake outputs derive from readDir — no flake edit), AGENTS.md, CONTRIBUTING.md, REUSE.toml.
  • check-skill-refs.py VERSION_EXEMPT_PARTS updated — load-bearing for CI.
  • Cross-references updated in 15 sibling skills + grok/android catalogue READMEs; each touched skill's bundles rebuilt in the same commit; old-name .zip/.skill removed.
  • Historical changelog entries keep the old name; references/CHANGELOG.md gains the v1.49 entry.

🤖 Generated with Claude Code

…1.49

The skill encoding now carries the document's canonical name. Renames
the directory and frontmatter name:, updates the catalogue (README §2,
AGENTS.md, CONTRIBUTING.md, REUSE.toml), the CI version-pin exemption
in check-skill-refs.py, and cross-references in fifteen sibling skills
plus the grok- and android-catalogue READMEs. Old-name bundles are
removed and every touched skill's bundles rebuilt in the same commit.
Historical changelog entries keep the name current when written.
Description unchanged at 988/1000. Standard-side PR:
Spacecraft-Software/Standard#28.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant