← ClaudeAtlas

starintel-spec-versionlisted

starintel, schema, versioning, release, lock, conformance
lost-rob0t/skills · ★ 0 · AI & Automation · score 62
Install: claude install-skill lost-rob0t/skills
# StarIntel spec version ## Goal Resolve and bump the active StarIntel document release without confusing the release/profile version with the immutable base schema version or filename. ## Input A StarIntel checkout containing `schema/starintel-schema.lock.json`, or a local canonical `starintel-gpt-auto-dig` checkout for release mutation. ## Output A verified current release/profile/base-schema tuple, or a scripted next-patch release bump followed by repository conformance checks. ## Workflow 1. **Resolve the lock before reading issue/docs version claims.** Prefer the current repository's `schema/starintel-schema.lock.json`. If absent, locate the applicable sibling `starintel-doc`/consumer lock; do not guess. 2. Resolve the current version with this skill's helper: ```bash python3 scripts/starintel_spec_version.py current \ --lock schema/starintel-schema.lock.json ``` The value to report as the current StarIntel spec/release is `release_version`, **not** `schema_version` and not a schema filename. 3. Follow `canonical_repository` + `canonical_commit` from the lock and verify the pinned manifest. Lock and manifest `release_version` must match. 4. Before any schema/profile change, inspect the canonical repository's repo-owned release tool: ```bash python3 scripts/schema-release.py current python3 scripts/schema-release.py check ``` 5. Release changes must use the canonical bump script. For the current release train the