Fig completion spec

fig-sbrs.ts is a completion spec for the sbrs command in the Fig format, the format of the withfig/autocomplete repository. Warp’s built-in completions, inshellisense and Amazon Q Developer CLI read specs from it. The file is prepared here, not submitted: nothing in this folder has been sent to upstream, and whether to send it is for the maintainer of this repository to decide.

What the file is#

• The output of sbrs completions fig of this branch (0.5.1). crates/cli/src/fig.rs writes it from the tables of the usage parser that reads the command line, so it lists the commands, aliases, options, required options, repeatable options and accepted words the parser accepts. A test (the_committed_fig_spec_matches_the_cli) fails when the file is stale. Until 0.3.0 clap_complete_fig wrote it.
• The file is the generator’s raw output, not formatted with the prettier settings of withfig/autocomplete (trailingComma: "es5", printWidth: 80). Upstream’s pnpm lint runs prettier --check, which the raw output fails; pnpm lint:fix in the steps below formats it, and the formatting only wraps long descriptions.
• It is the CLI of a build without the turso feature, which is how the Homebrew tap and a plain cargo install --path crates/cli build sbrs. sbrs report exists only with turso, so the spec has no report subcommand. The tui feature changes what some commands do, not the command line, so it does not matter here.
• 113 top-level subcommands (the 112 commands of sbrs --help and help) and 24 top-level options, -h and -V included. It uses template: "filepaths" in six places, and has no generators and no script, so it runs nothing in a user’s shell. Two descriptions contain a URL (https://example.com and http://localhost:4444), which upstream’s review bot lists.

To regenerate it after the CLI changes (the same test writes the usage spec and the CLI reference too):

SB_UPDATE_COMPLETIONS=1 cargo test -p seleniumbase-rs-cli --bin sbrs usage_spec

or, from an sbrs built without turso, sbrs completions fig > docs/completions/fig-sbrs.ts.

Where the spec and the CLI differ#

The generator reads the parser’s own tables, so it states what sbrs needs: an option is isRequired when the command line refuses to run without it, isRepeatable only when it collects a list (such as --features and --assert), and an argument is isOptional only when it may be left out. The clap_complete_fig file of 0.3.0 marked every option that takes a value as repeatable and every optional option’s value as optional, which did not match the parser.

The differences left are small: the help command is listed without the nested help <command> entries, the short options are listed as one name array with the long ones and never as combined flags, and the descriptions are the first line of the help text of each command, option and argument.

Before you decide#

Checked on 2026-10-15:

• withfig/autocomplete is not archived, but its last commit and last merged pull request are from 2025-05-05, and pull requests opened since (the newest from 2026-10-04) have not been merged. A new spec may wait a long time for a review, or never get one.
• The README says Amazon Q Developer CLI is the former Fig. The “How to Contribute” page it links (fig.io/docs/getting-started/contributing) answered with HTTP 503. The steps below come from the repository’s own README, CONTRIBUTING.md, package.json and workflows instead.
• There is no spec named sbrs, seleniumbase or similar in the repository.
• Contributors must sign a CLA (cla/cla.md; the bot asks for a pull request comment). Among other things it has you state that the work is yours.
• Without the upstream spec, sbrs completions bash|zsh|fish still gives shell-native completion, and Warp uses that by default (see CLI Usage).

What was checked on the file, and what was not:

• Checked: it loads as a module (Node 24 type stripping) with 113 subcommands, 24 options, six templates and two repeatable options; prettier parses it as TypeScript (prettier 3.2.5 here, upstream asks for ^3.4.2) and prettier --check with upstream’s settings reports only formatting differences, which pnpm lint:fix applies. A test compares the file with the generator’s output.
• Not checked: upstream’s pnpm test (tsc --noEmit against @withfig/autocomplete-types) and pnpm lint (eslint with @fig/eslint-config-autocomplete). They need a clone of withfig/autocomplete and pnpm install, which was not done. Run them in your fork before you open the pull request. pnpm dev (trying the spec live) needs the Amazon Q app.

Steps to submit#

Requirements from upstream: Node 20 or newer and pnpm 9 or newer.

# 1. Fork https://github.com/withfig/autocomplete on GitHub, then:git clone https://github.com/YOUR_GITHUB_USERNAME/autocomplete.gitcd autocompletegit remote add upstream https://github.com/withfig/autocomplete.gitgit fetch upstreamgit switch -c feat/sbrs-spec upstream/master# 2. Install, and add the spec as src/sbrs.tspnpm installcp /path/to/seleniumbase-rs/docs/completions/fig-sbrs.ts src/sbrs.ts# 3. Check it the way upstream's CI doespnpm lint:fix     # eslint --fix and prettier --writepnpm test         # tsc --noEmitpnpm build        # compiles src/ to build/# 4. Commit (conventional commit, the CLI's name as the scope, imperative,#    72 characters or fewer on the first line) and pushgit add src/sbrs.tsgit commit -m "feat(sbrs): add completion spec"git push -u origin feat/sbrs-spec

Then open the pull request against withfig/autocomplete master, with the text below. The CI jobs are a build, a linter (pnpm lint), a typecheck, a bot that comments with the spec’s URLs and scripts, and the CLA check: sign it by commenting I have read the CLA Document and I hereby sign the CLA on the pull request when the bot asks. If pnpm lint:fix changes the file, send the changed file, not the one in this folder.

Pull request text#

Title:

feat(sbrs): add completion spec

Description (tick the boxes that are true after you ran the checks):

Adds a completion spec for `sbrs`, the command-line tool of[seleniumbase-rs](https://github.com/MustCodeAl/seleniumbase-rs), a Rust port ofSeleniumBase (browser automation and testing).How it was made: `sbrs completions fig` writes the spec from the tables of theparser that reads the CLI's own definition, so the subcommands, aliases, options anddescriptions match `sbrs --help` of the default build (the optional `turso` featureadds a `report` subcommand, which the spec leaves out). The file was then formattedwith this repository's prettier settings (`pnpm lint:fix`). To regenerate it:`sbrs completions fig`.- 113 top-level subcommands, `help` included.- `template: "filepaths"` only; no generators and no `script`.- Short and long forms share one `name` array; there are no combined short flags.Checklist from the greeting comment:- [ ] Do all subcommands / options which take arguments include the `args` property?      The generator writes `args` for every option and argument the CLI defines.- [ ] Are all options modular (`-a -u -x`, not `-aux`)?- [ ] Have all other checks passed (`pnpm lint`, `pnpm test`, `pnpm build`)?

Install sbrs with cargo install --path crates/cli in this repository, or from the Homebrew tap, to run the generator yourself.