Fireskill CLI Overview

The Bun and TypeScript command line that handles the mechanical parts of the Fireskills flow.

The Fireskill CLI does the mechanical parts of the flow: it moves specs between states, records the effort score, runs a quick spec linter, shows progress, syncs milestones and manages lessons learned. Its code is in fireskills/cli/ and you call it from the repository root:

bun run fireskill <command> [arguments] [options]
bun run fireskill --help

The root package.json maps fireskill to bun fireskills/cli/src/main.ts. The CLI is derived from the Specsfy CLI (MIT license), reduced to the flow engine: it has no installer, catalog or updater, because skills and specialists already live in the repository.

Things to know

  • In the flow, the skills call the CLI for you. You run it yourself to look at the state or to fix something by hand.
  • Every command takes --project <path> (default: the current directory) and most take --json.
  • Spec commands identify a spec by its number (0001) or its full directory name (0001-convite-de-membros-por-e-mail).
  • The CLI is written in TypeScript with commander and needs bun. In a clean copy, bun install --cwd fireskills/cli installs its own dependency.
  • State changes are written atomically (a temporary file, then a rename).
  1. Command reference: every command, its arguments and real output.
  2. Governance and safety scripts: monitor_context.mjs and check_database_safety.mjs, which are scripts of the skills, not CLI commands.
Nuxfire Production Kit

Ready to build and launch your SaaS?

Get 100% full source code ownership, zero proprietary wrappers, and architecture engineered for millions of requests on Cloudflare.

© 2026 Nuxfire