Build Internal CLI tools using Fig Scripts

Top engineering orgs, like Shopify, Brex, Slack, maintain internal CLI tools to boost developer productivity. Now, with Fig Scripts, your team can have the same 10x developer experience with a fraction of the work.

Why build CLI tools for your team?

Teams use internal CLI tools to codify terminal workflows and improve developer productivity.

• • It let new engineers focus on getting up to speed with their new projects, not messing around figuring out how various systems fit together.

• • It helped everyone stay in the flow and focused on their tasks at a higher level.

• • It reduced the amount of edge-case “stuff” floating in developers’ brains from day-to-day (“ugh, where do the log files live again?”).

• • Improvements made by one person made everyone’s work easier.

How does it works?

Go to Fig Scripts and create a New CLI. Once you create a CLI tool, everyone on your team will have be able to run use it.

Using the Fig Dashboard, you’ll be able to add new commands & modify the structure of the CLI tool. Changes you make are automatically shared with your entire team.

You can move existing Fig Scripts into your CLI tool or you can create new commands as needed.

Build your team’s internal CLI tool with Fig

Fig Scripts is the easiest way to create internal CLI tools and share scripts across your engineering team. You can build and distribute an internal developer tool in less than 5 min.

• • Automatic provisioning makes it easy to distribute your CLI tool and push changes, without writing your own self-updating logic and backend.

• • Out-of-the-box error reporting and usage monitoring lets you gain insights into blockers, helping your team move faster.

• • Interactive terminal UIs adds helpful guardrails to the execution process, preventing mistakes and enabling new engineers to get up to speed quickly.

If you have any feedback or want a Fig engineer to help onboarding your team, don’t hesitate to reach out to hello@fig.io.