release-builder

Build, audit, and publish project artifacts to web, desktop, or CLI release channels.

Updated Jun 29, 2026
One-click install
npx skills add https://github.com/iJosueeh/amauta --skill release-builder-ijosueeh
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: release-builder
Source: https://github.com/iJosueeh/amauta/tree/main/.opencode/skills/release-builder
Command: npx skills add https://github.com/iJosueeh/amauta --skill release-builder-ijosueeh

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Shipping a project involves more than a successful build: version mismatches, leaked credentials in artifacts, missing rollback plans, and untested installs cause most release failures. This Skill runs the full build-package-test-publish lifecycle with enforced privacy audits, smoke tests, and rollback strategies so releases are verifiable before they go live. ## Core Features & Use Cases - Channel-specific release strategies: Separate workflows for Web (Vercel/Netlify deploy), Desktop (Electron packaging with signing/notarization), and CLI (npm publish) projects. - Privacy and security audit: Greps build artifacts for developer paths, API keys, database files, and credentials before packaging, and blocks the release on any leak. - Quality gates and scoring: An 8-dimension, 16-point quality rubric (build integrity, smoke test, version consistency, rollback plan, etc.) with a ship threshold of 12 points. - Use Case: After finishing a Vite web app, invoke the skill to bump the version, run a clean build, scan dist/ for leaked secrets, deploy to Vercel, smoke test the live URL, and create a matching git tag and GitHub Release. ## Quick Start Ask the agent to release the current project to your chosen channel, for example: run /release-builder web to build, audit, and deploy the app to production.

Frequently Asked Questions about release-builder

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

FAQPage Schema
How do I release a web project to Vercel or Netlify?▼

The skill detects the project type, runs the build, audits the output directory for leaked secrets, then deploys with vercel --prod or netlify deploy --prod. After deployment it verifies the live URL loads and smoke tests core features before tagging the release.

How do I publish a CLI package to npm?▼

The CLI release flow builds the artifacts, runs a privacy audit, checks npm whoami authentication, then runs npm publish. It finishes with a global install test (npm install -g) and smoke tests each core command.

Does the release process check for leaked API keys in build artifacts?▼

Yes. The privacy audit greps the build output directory for patterns like sk-ant-, sk-proj-, API_KEY, developer paths (/Users/, C:\Users), .env files, database files, and credential files. Any finding stops the release until fixed.

What happens if a release fails after publishing?▼

The rollback strategy reference defines per-channel recovery: vercel rollback or dashboard restore for web, npm deprecate or unpublish (within 72 hours) for CLI, and fix-repackage-re-release for desktop installers. A rollback plan must be defined before publishing.

When should I not use this release workflow?▼

Do not use it for writing features, fixing bugs, or reviewing code quality; those belong to development and code-review skills. It also requires existing project code and a package.json, so empty projects must be built first.