# A Simple Go CLI for Organizing Ad-Hoc Developer Tools

DevFeed: [A Simple Go CLI for Organizing Ad-Hoc Developer Tools](<https://devfeed.tech/articles/the-simplest-cli-that-could-possibly-work-35472.md>)

Original publisher: [Read original article](<https://darkcoding.net/software/the-simplest-cli-that-could-possibly-work/>)

Author: Graham King

Published: 2020-06-06T18:12:06Z

Content type: opinion

Language: en

Sources: [Graham King](<https://devfeed.tech/sources/graham-king.md>)

Topics: [Command-line interface](<https://devfeed.tech/topics/cli.md>), [Go Language](<https://devfeed.tech/topics/go-language.md>), [Tooling](<https://devfeed.tech/topics/tooling.md>), [Development](<https://devfeed.tech/topics/development.md>)

Tags: [cli](<https://devfeed.tech/tags/cli.md>), [command-line](<https://devfeed.tech/tags/command-line.md>), [dependencies](<https://devfeed.tech/tags/dependencies.md>), [go](<https://devfeed.tech/tags/go.md>), [software](<https://devfeed.tech/tags/software.md>), [tooling](<https://devfeed.tech/tags/tooling.md>)

## AI overview

The article describes organizing ad-hoc command-line utilities in a single Go binary. It uses a map of functions, with each command defining its own flags, printing errors, and documenting its usage, avoiding an external CLI framework dependency.

## Source excerpt

In Go, what's the simplest possible way to put all your ad-hoc tools in one place?