release-admin

Archive, restore, hard-delete, or repair tracker links on Marshall projects, releases, and components.

Updated Jul 15, 2026
One-click install
npx skills add https://github.com/builtbyberry/marshall-claude-plugin --skill release-admin-builtbyberry
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: release-admin
Source: https://github.com/builtbyberry/marshall-claude-plugin/tree/main/marshall/skills/release-admin
Command: npx skills add https://github.com/builtbyberry/marshall-claude-plugin --skill release-admin-builtbyberry

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Release records in a shared Marshall store sometimes get mis-created, abandoned, or lose their tracker links, and there is no safe corrective path that distinguishes reversible hiding from irreversible deletion. This Skill provides the corrective verbs — archive, unarchive, hard delete, and tracker-link repair — with the store's server-side guards explained so you never destroy real history. ## Core Features & Use Cases - Reversible archive/unarchive: Hide projects, releases, or components from active views while preserving the row and audit trail, with bottom-up archive and top-down restore ordering. - Fenced hard delete: Permanently remove only mis-created empty records, guarded server-side by owner-only and empty-only checks that name the exact blockers on refusal. - Tracker link repair: Re-link releases and components whose Linear tracker records were never filed, with resumable passes that never create duplicates. - Use Case: A release was created against the wrong version and is cluttering the active list — confirm with the operator, archive it reversibly, and report the exact unarchive call that undoes it. ## Quick Start Use the release-admin skill to archive the release version 2.4.0 that was created by mistake and tell me how to undo it.

Frequently Asked Questions about release-admin

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

FAQPage Schema
How do I archive a release in Marshall?

Call archive_release with the release version-or-slug, adding the project slug if the version is ambiguous. Archive is reversible and available to any workspace member, but the store refuses with cannot_archive while the release holds active components.

What is the difference between archive and hard delete in Marshall?

Archive is a reversible hide that preserves the row and audit trail, while hard delete is an irreversible removal with no undo. Hard delete is owner-only and only succeeds on empty records with no components, findings, or deploy records.

How do I fix a release that came back unlinked from the tracker?

Run repair_tracker_link with the release version and optional project slug. It resolves provable links, files missing issues, and refuses anything it would have to guess; re-run it only when the response says resumable is true.

Why does hard_delete_release refuse with cannot_delete?

The store refuses unless the release has zero components, zero findings, and no deploy record, and the error names the exact blockers. The correct next move is almost always to archive the release instead of working around the guard.

Does unarchiving a project restore its releases and components?

No, unarchive does not cascade. Restoring a parent leaves its archived children hidden, so you must unarchive each release and component level you actually want back, working top-down.

When should I cancel a component instead of archiving it?

Use the cancelled work-state via set_component_state when work was deliberately cut, since that keeps it visible and correctly strands dependents. Archive only when the record no longer needs to appear on screen.