promote

Name: promote
Availability: InStock
Author: ameng2001

Finalize production plugin manifests and archive approved design workspaces.

1|Updated Mar 27, 2026

Search Tags:#versioning #release workflow #workspace lifecycle #plugin promotion #manifest finalization #design snapshot

Ready to run

npx skills add https://github.com/Ameng2001/astra-studio-plugins --skill promote-ameng2001

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: promote
Source: https://github.com/Ameng2001/astra-studio-plugins/tree/main/studio-core/skills/promote
Command: npx skills add https://github.com/Ameng2001/astra-studio-plugins --skill promote-ameng2001

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Promote turns an approved, tested plugin workspace into a production-ready, versioned milestone so you can ship confidently while keeping the design history for the next iteration.

Core Features & Use Cases

Finalize the production manifest: Converts plugin.json.draft into {target_dir}/.claude-plugin/plugin.json, bumps the patch version (or uses an explicitly provided version), and wires up skills/, commands/, hooks/, and mcpServers based on what exists in the target.
Snapshot design documents: Copies the plugin’s active design workspace from studio/changes/{name}/ into an archived iteration directory, updating the archived and active status.json files to reflect shipped vs continued work.
Guardrail pre-checks: Ensures the plugin is in approved phase and that all in-scope skills have tested status before promoting.

Quick Start

Promote your approved plugin by running: promote your-plugin-name.

Frequently Asked Questions about promote

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I finalize a plugin manifest for a production release?▼

Finalizing a plugin manifest for release involves converting `plugin.json.draft` into production `plugin.json`, bumping the patch version or applying an explicit version, and wiring up `skills/`, `commands/`, `hooks/`, and `mcpServers` based on target directory contents.

What is the best way to archive design documents after a plugin release?▼

Archiving design documents after a release is handled by snapshotting the active design workspace from `studio/changes/{name}/` into a dated iteration archive directory. This process updates both active and archived `status.json` files to distinguish shipped milestones from continued design work.

What prerequisites are needed to promote a plugin version?▼

Prerequisites for promoting a plugin version require the workspace to be in the `approved` phase in `studio/changes/{name}/status.json`. Guardrail pre-checks verify all in-scope skills hold `tested` status and the implementation exists under the target directory.

How does design snapshot versioning work during plugin promotion?▼

Design snapshot versioning during plugin promotion copies the active design workspace from `studio/changes/{name}/` into a date-and-iteration archive directory. It updates archived and active `status.json` files to reflect shipped versus ongoing work.

Why does plugin promotion fail when status is not approved?▼

Plugin promotion fails when not approved because guardrail pre-checks require `studio/changes/{name}/status.json` to be in the `approved` phase. The workflow also verifies all in-scope skills have reached `tested` status before proceeding.