One key, or two?
Launching sigillum, a standalone artefact signing and verification CLI, and the Rust signing problem that made it necessary.
Tags
21 pages
CLI
The scaffolder that won't hand you code that doesn't compile
A Rust scaffolder with an AI codegen path that drafts a real command, then refuses to hand it over until it compiles and passes lint.
A flag is not a setting
Reviewing a scaffolder turned up a command name that quietly conflated two different things. A flag and a setting are not the same object.
The cobra hook I was sure I'd enabled
An audit found that a Cobra option had never been enabled, so the root command hooks had silently not run on any subcommand for months.
Generate a command from a script or a sentence with go-tool-base
Generating a Go command from a shell script or a plain sentence, and the repair agent that has to make the result build before you see it.
Building a CLI with go-tool-base, part 5: a CLI that updates itself
Add self-update to a Go CLI: resolve releases per platform, compare versions, verify checksums and migrate config on upgrade.
Building a CLI with go-tool-base, part 4: an AI dungeon master
Build an AI dungeon master in Go: keep the model to prose only by putting the rules in the system prompt and the mechanics in typed tool calls.
Building a CLI with go-tool-base, part 3: expose your CLI to AI agents
Expose an existing Go CLI to AI agents over MCP without writing any AI code, using built-in commands. The agent reach equals the CLI reach.
Building a CLI with go-tool-base, part 2: configuration your tool can trust
Configuration for a Go CLI: precedence of flags over env over files, per-command embedded defaults, layered config merging and a strict mode.
Building a CLI with go-tool-base, part 1: scaffold and your first command
Install gtb, scaffold a releasable Go project, understand the generated and owned file split, then add your first command and run it.
