production-build

Build the AlgoBooth production installer with tauri and report its path.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/jacobrocks1212/claude-config --skill production-build
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: production-build
Source: https://github.com/jacobrocks1212/claude-config/tree/main/repos/algobooth/.claude/skills/production-build
Command: npx skills add https://github.com/jacobrocks1212/claude-config --skill production-build

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill automates building the real production installer for AlgoBooth on a dedicated test machine and surfaces an unsigned installer for manual smoke testing. It wraps the repo-root script test-production.ps1, which performs a pull, conditional dependency installs, a tauri build, and opens the resulting installer for handoff.

Core Features & Use Cases

  • End-to-end production build: pull current checkout, install dependencies as needed, run tauri build, and generate the installer for QA.
  • Flexible workflow: map user-provided flags to the script's switches to control install, clean, skip-pull, and no-install-deps behaviors.
  • Observability: report source update status (commit SHAs), build outcome, and the installer path (target/release/bundle) for easy handoff.
  • Guardrails: ensure a clean working tree and warn about unsigned build status; provide diagnostic guidance on failures.

Quick Start

Run the production-build skill on the test machine to generate the production installer and hand it off for smoke testing.

Frequently Asked Questions about production-build

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

FAQPage Schema
How do I build a Tauri production installer for smoke testing?

This skill automates building a Tauri production installer by pulling the latest source, installing dependencies, compiling the bundle, and surfacing the final installer path under target/release/bundle for manual smoke testing.

What does a Tauri production build process include?

A Tauri production build process includes pulling current source commits, conditionally installing dependencies, compiling the application via tauri build, and reporting the final installer location for manual verification.

Can I skip dependency installation during a Tauri production build?

Yes, you can skip dependency installation during a Tauri production build by mapping user-provided CLI flags to the script's no-install-deps switch, allowing you to bypass redundant installs on subsequent runs.

Does the Tauri build script require a clean working tree?

Yes, the Tauri build script requires a clean working tree to ensure build integrity, providing guardrails that warn about uncommitted changes before pulling source updates and generating the installer.

Why does my production build generate an unsigned installer?

The production build generates an unsigned installer specifically for manual smoke testing on a dedicated test machine, providing diagnostic guidance and build status reports while warning about the unsigned build status.