sakura-release

Prepares and verifies clean user-ready release artifacts from a known source state.

3|1|Updated Sep 9, 2026
One-click install
npx skills add https://github.com/v20227/using-sakura-dev --skill sakura-release-v20227
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: sakura-release
Source: https://github.com/v20227/using-sakura-dev/tree/main/skills/sakura-release
Command: npx skills add https://github.com/v20227/using-sakura-dev --skill sakura-release-v20227

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Shipping software often mixes development records, secrets, and debug leftovers into deliverables, or confuses a working dev build with a verified release. This Skill prepares a clean, verified artifact that another person can directly open, install, or use. ## Core Features & Use Cases - Delivery Target & Version Policy: Determines whether the goal is a prototype, release candidate, or published release, and applies the project's version increment rules tied to commits. - Artifact Cleanup: Excludes .sakura/ development records, secrets, local paths, caches, and debug output while preserving required licenses, notices, and runtime assets. - Artifact Verification: Inspects the actual built archive or installer, checks integrity and contents, runs the critical user path, and records version, source state, and known limitations. - Use Case: Before handing a project to a client, ask for a clean version; the Skill builds from a known commit, strips internal development records, verifies the artifact contents, and reports exactly how to open it. ## Quick Start Prepare a clean release version of this project that another person can install, and verify the artifact before delivery.

Frequently Asked Questions about sakura-release

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

FAQPage Schema
How do I prepare a clean release version of my project?▼

Describe the delivery target such as a clean version, installer, or release candidate. The Skill builds from a known commit, excludes development records and secrets, inspects the actual artifact, and verifies the critical user path before reporting the result.

How to exclude development records from a release archive?▼

The Skill unconditionally excludes the project's `.sakura/` directory and equivalent internal records like working PRDs, task state, and repair logs from every artifact. It prefers explicit packaging include sets over archiving the whole working folder.

Does it verify the built artifact or just the source tree?▼

It inspects the actual produced artifact, not just ignore files or packaging configuration. Release verification fails if internal development records appear in the archive, and the inventory and content digest are recorded.

How are version numbers incremented for releases?▼

The display version advances once per commit or completed bug fix, included in the same commit as the triggering work. Projects with an explicit version policy keep their own sequence; uncommitted edits and test reruns never increment it.

When does a release get marked as deployed or published?▼

The status stays RELEASE_CANDIDATE until the user-facing artifact passes all required checks. DEPLOYED or PUBLISHED is claimed only after the external action actually occurred and its result was observed.