Skip to main content
Bach ships a skill for coding agents, so an agent can package a Windows app without you explaining Bach first. The skill is a single SKILL.md that teaches the commands, the config and the safety habits.

Install the skill

The skill lives at skills/bach/SKILL.md in the repository.

What the skill teaches

  • How to get the bach command on Windows, macOS and Linux, with npm install --global @usebach/cli or the install scripts, never with administrator rights, and to run bach doctor.
  • How to find or produce the one folder Bach installs, for Rust, Electron, Tauri, .NET, Go and PyInstaller apps.
  • How to write bach.toml from the project’s own metadata instead of inventing a name, version or publisher, and to never change [app] id after a release.
  • To run bach check, treat every warning: as something to fix or mention, and look at the window with bach preview.
  • To build with bach build, then sign, then write the feed or winget manifests.
  • To add the one-click release with bach workflow instead of writing a workflow by hand, and to raise versions with bach version instead of editing several files. See One-click releases.

Safe habits for agents

Never run a real install of the built setup file on someone’s machine unless they ask.
  • Use bach preview to see every page. It pretends each step and changes nothing.
  • When a real end-to-end test is wanted, use a silent install and remove it again afterwards: Setup.exe --silent, then uninstall.exe --silent.
  • Read the log at %TEMP%\<app id>-setup.log when something fails instead of guessing.
  • Fix the setting that bach check names. Do not work around the checker.

Read these docs as Markdown

Every page of this site can be copied as Markdown or opened in an AI assistant from the contextual menu at the top of the page.