close

Skill Provenance: Close

Update all version-tracking artifacts when finishing a skill editing session. This ensures the bundle leaves the session in a consistent, verifiable state.

When to use

Run /skill-provenance:close after you've finished editing files in a skill bundle and before committing, packaging, or handing off.

Protocol

1. Validate before mutation. Run verify-only validate.sh first when available. Resolve structural grammar, unsafe or duplicate paths, symlink components, missing files, and unlisted files before updating hashes. Add a manifest entry for each new file; --update never adds unlisted files. Hash mismatches and missing or malformed hashes may then be repaired with an explicit validate.sh --update workflow; hash: null remains an intentional opt-out.

2. Update internal version headers. For each changed file that carries YAML frontmatter with version metadata:

   • Increment version by 1.
   • Set version_date to today.
   • Set previous_version to the old version number.
   • Write a change_summary (1-3 sentences describing what changed, not just that something changed).

3. Update MANIFEST.yaml. For every changed versioned file:

   • Update version to match the new internal version.
   • Recompute and update hash.
   • For files that don't carry internal headers (JSON, scripts, binaries), the manifest version field is authoritative — increment it there.
   • Bump bundle_version (semver): PATCH for fixes/docs, MINOR for new features, MAJOR for breaking changes.
   • Update bundle_date to today.
   • If the user deployed or reinstalled the skill this session, update relevant deployments metadata.

4. Update CHANGELOG.md. Add a new entry at the top:

   • Use the new bundle_version and today's date as the heading.
   • Name every file that changed and what changed in it.
   • Flag staleness explicitly. If a versioned file was changed but a dependent file was not updated (e.g., SKILL.md changed but evals.json wasn't updated to match), say so in the entry.