meticulous-cli-schema
meticulous schema
meticulous schema [command..]
Purpose: Output the CLI command schema as JSON — designed for agent and programmatic use. Returns the structure of available commands (names, descriptions, subcommands, and options) without executing anything.
Options
| Option | Type | Description |
|---|---|---|
command |
positional (variadic) | Zero or more command path segments to drill into a specific command |
Output Format
Without arguments, outputs a JSON array of all top-level command objects:
[
{ "command": "auth", "describe": "Authentication commands", "subcommands": [...] },
{ "command": "ci", "describe": "CI/CD commands", "subcommands": [...] },
...
]
When targeting a specific leaf command (no subcommands), the full option schema is included:
{
"command": "simulate",
"describe": "Replay a recorded session",
"options": {
"sessionId": { "type": "string", "required": true },
"appUrl": { "type": "string" },
"headless": { "type": "boolean", "default": false },
...
}
}
Examples
# List all top-level commands (structure only, no options)
meticulous schema
# Show the full option schema for a specific command
meticulous schema simulate
meticulous schema download replay
meticulous schema ci run-with-tunnel
# Show subcommands for a command group
meticulous schema ci
meticulous schema auth
Use in Agent Workflows
The schema command is the recommended way for an agent to discover what commands exist and what options they accept before constructing a meticulous invocation:
- Run
meticulous schemato get the command tree. - Run
meticulous schema <command>to get the full option list for the target command. - Construct the command with the required options.
- Optionally add
--dryRunto verify the constructed invocation before executing it.
More from alwaysmeticulous/skills
meticulous-cli
Overview of the Meticulous CLI tool and its global options. Use when asking about the meticulous CLI in general, available commands, or global flags that apply to all commands.
25test-with-meticulous
Run after implementing any frontend change to verify its visual impact. Triggers a Meticulous test run, then inspects screenshot diffs to classify each visual change as intended or unintended. Use this before marking a frontend task as complete.
21meticulous-simulate-and-diff
Run a Meticulous session simulation against a live URL and analyze the visual output — either by inspecting screenshots directly (quick-check mode) or by comparing pixel and HTML diffs against a base replay. Use when checking whether a code change has introduced visual regressions for a specific session.
20meticulous-cli-download
Meticulous CLI download commands for fetching recorded sessions, replays, and test runs to the local data directory. Covers `meticulous download session`, `meticulous download replay`, and `meticulous download test-run`.
19meticulous-cli-auth
Meticulous CLI authentication commands. Use when logging in, checking who is authenticated, or logging out of the Meticulous CLI. Covers `meticulous auth whoami` and `meticulous auth logout`.
19meticulous-cli-project
Meticulous CLI project commands for inspecting the project configuration linked to an API token. Covers `meticulous project show`.
19