메뉴
End-to-end release orchestration for SkillMeat. Routes five intents (version bump, regen openapi, regen SDK, audit coverage, rollover changelog) to the single linear release-orchestration workflow. Use when running /release:bump or coordinating a tagged release.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Token-efficient tracking for AI orchestration. CLI-first for status updates (~50 tokens), agent fallback for complex ops (~1KB). Use when: updating task status, querying blockers, creating progress files, validating phases.
Use when changing artifact identity, versioning, manifests, search/matching, content resolution, repository interfaces, or the local/enterprise DB split in the SkillMeat codebase (skillmeat/core/, skillmeat/cache/, skillmeat/storage/, skillmeat/sources/) — i.e. the informal "Registry Core" kernel this AOS has not yet named as a literal module. Trigger keywords: registry core, artifact identity, repository interface, IArtifactRepository, ICollectionRepository, RepositoryFactory, cache.db, SKILLMEAT_EDITION, alembic multi-head, schema drift, cli_snapshot.json, deprecation window, backward compatibility, breaking change to core. Do NOT use for CLI-surface/agent-facing command routing (use `skillmeat-cli`), for BOM/attestation authoring (use `asdlc-skillbom-builder`), or for bundle/deployment-set packaging (use `asdlc-sam-artifact-packager`).
Use when packaging SkillMeat artifacts (skills, agents, commands, context entities, bundles, deployment sets, or project-starter templates) for deployment or distribution — creating a bundle (`skillmeat bundle create`/`add-member`), building and publishing a `.skillmeat-pack` round-trip (`bundle build-pack`/`publish-pack`/`export`/`import`), assembling a deployment set (`deployment-set create`/`add-member`/`deploy`), registering a project-starter scaffold template (`template create`), deploying a single artifact (`skillmeat add`, `skillmeat deploy`), or taking a safety snapshot before a risky change (`skillmeat snapshot`/`rollback`). Covers local-collection vs enterprise-edition packaging differences and post-deploy verification. Do NOT use for generating BOM/attestation provenance — use `asdlc-skillbom-builder` first. Do NOT use for pre-packaging quality review — use `asdlc-skill-review-board` first.
Use when an agent needs to produce SkillBOM provenance for skills, agents, commands, or other SkillMeat artifacts — generating a BOM snapshot (`skillmeat bom generate`), signing or verifying it with Ed25519 (`skillmeat bom sign|verify|keygen`), wiring git hooks that link commits to BOM state (`skillmeat bom hook install`), inspecting materialization sidecars for parameterized deploys (`skillmeat bom materializations`), or recording an owner-scoped attestation (`skillmeat attest create|list|show`). Covers exactly what fields a SkillBOM entry carries, how BOM ties into git history, and the honest gaps in promotion/approval status and policy enforcement. Do NOT use this skill for packaging artifacts into bundles/deployment-sets/templates — use `asdlc-sam-artifact-packager` instead. Do NOT use for pre-packaging quality review — use `asdlc-skill-review-board` first.
Answer CCDash project-intelligence questions using the shipped MCP tools when available and the in-repo `ccdash` CLI otherwise. Use when the operator or another agent asks about project status, feature forensics, workflow failure patterns, after-action reports, session intelligence (transcripts, search, detail), runtime validation posture, CLI timeout or caching behavior, container project onboarding, watcher binding, or how to troubleshoot the shipped CCDash API/worker/MCP surfaces. Keep routing aligned with the current shipped runtime contract and repo docs.
Audits CHANGELOG coverage for a git commit range; read-only — surfaces gaps for human remediation. Use this skill before a version bump, in CI, or ad-hoc to verify that all non-trivial commits are reflected in the changelog. Co-loaded with the release skill on every /release:bump invocation. Does not write or modify any files; outputs structured gap reports and exit codes only.
| name | release |
| description | End-to-end release orchestration for SkillMeat. Routes five intents (version bump, regen openapi, regen SDK, audit coverage, rollover changelog) to the single linear release-orchestration workflow. Use when running /release:bump or coordinating a tagged release. |
| version | 1.1 |
| updated | "2026-04-27T00:00:00.000Z" |
| spec | ./SPEC.md |
Orchestration guidance for executing a complete, validated SkillMeat release — from version bump through git tag and GitHub release creation.
Load this skill when:
/release:bumpAlways co-load with changelog-sync when invoked via /release:bump (required pair per CLAUDE.md Command-Skill Bindings).
| Intent | Workflow Section | Canonical Spec |
|---|---|---|
| Bump the project version to a new semver | workflows/release-orchestration.md §Step 1: Version Bump | .claude/specs/version-bump-spec.md |
Regenerate openapi.json from the live app | workflows/release-orchestration.md §Step 2: Regen OpenAPI | skillmeat/api/CLAUDE.md §Endpoint Inventory Maintenance |
Regenerate SDK client from openapi.json | workflows/release-orchestration.md §Step 3: Regen SDK | .claude/specs/version-bump-spec.md §3. OpenAPI Spec + Generated SDK |
| Audit CHANGELOG coverage before tagging | workflows/release-orchestration.md §Step 4: Audit Gate | .claude/specs/changelog-spec.md |
Roll over [Unreleased] to versioned section | workflows/release-orchestration.md §Step 5: Rollover Changelog | .claude/specs/changelog-spec.md, .claude/specs/version-bump-spec.md §CHANGELOG Roll-Forward |
| Check skill alignment with new version | workflows/release-orchestration.md §Step 10: Skill Alignment | .claude/specs/version-bump-spec.md §6. Skill SPEC.md alignment |
| Commit, tag, and create GitHub release | workflows/release-orchestration.md §Step 7–9: Commit, Tag, Release | .claude/specs/version-bump-spec.md §Git Tagging |
For a full release, read workflows/release-orchestration.md and follow the steps in order. The workflow is a single linear flow — steps are not optional and cannot be reordered.
Dry-run (non-destructive preview through Step 5):
# Dry-run everything up to and including changelog rollover
python .claude/skills/release/scripts/rollover-changelog.py \
--version X.Y.Z --date YYYY-MM-DD --dry-run
Steps 7–9 (commit, tag, release) are always destructive; confirm with the operator before executing.
audit-coverage.py must exit zero before a tag is created. If it exits non-zero:
[Unreleased] to cover the flagged commits, then re-run.The --force flag bypasses the audit gate. Agents must never pass --force without an explicit human instruction in the current conversation. When a human operator passes --force, the workflow must print a visible warning and ask for confirmation before continuing. See workflows/release-orchestration.md §Force-Bypass Protocol.
audit-coverage.py exit zero is a hard prerequisite.version-bump-spec.md is the authoritative list of bump targets — do not add targets here.rollover-changelog.py) must complete before git tag is created.Full invariant set: SPEC.md §3. Invariants & Constraints
A commit-msg hook warns (but never blocks) when a user-facing commit is made without a corresponding [Unreleased] CHANGELOG entry.
# Run from the repository root
ln -s ../../.claude/hooks/check-changelog-entry.sh .git/hooks/commit-msg
The symlink is relative so it survives directory renames. Uninstall by removing .git/hooks/commit-msg.
chore, refactor, test, docs, ci, build, style, merge commits, version bumps).CHANGELOG.md is staged with an [Unreleased] diff line.[Unreleased] update is staged, prints a warning to stderr and exits 0.SKILLMEAT_SKIP_CHANGELOG_CHECK=1 git commit ...
| File | Purpose |
|---|---|
.claude/hooks/check-changelog-entry.sh | Shell wrapper (symlink target) |
.claude/hooks/check-changelog-entry.py | Python helper with detection logic |
tests/unit/skills/test_check_changelog_entry.py | Test suite (36 cases) |
Full specification: .claude/specs/changelog-spec.md §Pre-commit Hook
./workflows/release-orchestration.md./SPEC.md.claude/specs/version-bump-spec.md.claude/specs/changelog-spec.md.claude/skills/release/scripts/audit-coverage.py.claude/skills/release/scripts/rollover-changelog.py